# Excel Spreadsheet to an App Your Field Team Uses on Phones > Your techs cannot run a 40-column spreadsheet on a 6-inch screen. Three ways to turn it into a phone app, what each costs, and a one-week rollout plan. Source: https://llamapress.ai/how-to-turn-an-excel-spreadsheet-into-an-app-your-field-team-can-use-on-their-phones | Updated: 2026-09-02 --- [LlamaPress Blog](https://llamapress.ai/blog) Your techs cannot run a 40-column spreadsheet on a 6-inch screen. Three ways to turn it into a phone app, what each costs, and a one-week rollout plan. [Back to all articles](https://llamapress.ai/blog) ![Kody Kendall](https://llamapress-ai-image-uploads.s3.us-west-2.amazonaws.com/jujc1ep8nuqrdiftdfer1ngp833u) Written by ### Kody Kendall AI & Software Engineer | Creator of the Leonardo Coding Agent Updated September 2026 You have three ways to put an Excel spreadsheet on your field team's phones. Route one is the Excel mobile app, which suits one tech doing read-only lookups. Route two is a no-code builder laid over the sheet, such as Google AppSheet (from $5 per user per month) or Glide (from $25 a month), as of September 2026. Route three is an AI-built web app, the spreadsheet rebuilt as job screens on a real database and installed to the home screen. That route costs from $9.99 a month hosted or $2,000 built for you. For three or more techs who need photos, status buttons, and offline entry, route three is the one that lasts. In short - The Excel mobile app shows a 40-column grid on a 6-inch screen, so techs scroll sideways, type into the wrong row, and overwrite each other. - A field app needs one job per screen, big status buttons, photo upload tied to the job, a signature box, and an offline queue. - Your Jobs tab becomes the job list, one row becomes the job screen, and the Status column becomes the buttons. - As of September 2026, AppSheet costs $5 to $20 per user per month and Glide $25 to $125 a month. A LlamaPress web app costs $9.99 to $54.99 a month with no per-user fee. - Roll the app out to two techs for one week, fix the three things they complain about, then give it to everyone. I build these apps. I created Leonardo, the AI coding agent behind LlamaPress, and I have watched it turn more than 400 spreadsheets into apps. Field team spreadsheets are the most common kind I see. The file is usually a Jobs tab with 30 to 40 columns, kept by one person in the office. The techs read it on a phone in a truck, pinch to zoom, and call the office with anything they need to change. ![Two construction workers in hard hats reviewing job details on a tablet at a work site](https://images.unsplash.com/photo-1778074762022-c33cc42f79ae?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w4NTU2MDF8MHwxfHNlYXJjaHwzfHxjb250cmFjdG9yJTIwdGFibGV0JTIwY29uc3RydWN0aW9uJTIwc2l0ZXxlbnwwfHx8fDE3ODgzNjE4OTJ8MA&ixlib=rb-4.1.0&q=80&w=1080) Photo by [alan boyce](https://unsplash.com/@abcpac?utm_source=leonardo_rails_app&utm_medium=referral) on [Unsplash](https://unsplash.com/photos/two-construction-workers-review-plans-on-a-tablet-gyrKtgqMChY?utm_source=leonardo_rails_app&utm_medium=referral) ## Why does the Excel mobile app fail in the field? The Excel mobile app fails because a spreadsheet is a grid built for a 27-inch monitor. On a 6-inch phone screen a tech sees four columns and twelve rows at a time. Your Jobs tab has 40 columns. The address is in column C, the gate code in column N, and the status in column R. The tech scrolls sideways, loses the row, and types the completion note into the job above. Saving is the second problem. Excel saves the whole file, never one row. Microsoft's documentation on offline use says a file on OneDrive or SharePoint must have been opened online at least once. The same page says changes sync "as soon as you are back online." A tech in a basement edits row 14. The office edits row 14 at the same time. When the tech gets signal, one of those edits loses. We wrote up the same failure for warehouses in [the inventory overwrite problem](https://llamapress.ai/people-keep-overwriting-each-other-in-our-inventory-spreadsheet-here-is-the-fix). Microsoft's own page on the mobile apps also sets a licensing line. Without a Microsoft 365 subscription, the mobile Excel app lets you "create and view files" and "do basic editing" for non-business accounts and files. Advanced editing requires a subscription. So every tech who edits a business file needs a paid seat, and the screen problem remains. The last three gaps have no workaround inside Excel. A photo of the finished work lands in the camera roll, and the cell holds a filename someone typed. There is no GPS or time stamp on the row, so "arrived 8:05" means whatever the tech remembers on Friday. A customer cannot sign a cell. ## What does a field team app have to do? A field team app has to do one job per screen with buttons a gloved thumb can hit. That is the whole design brief. The tech opens the app and sees today's jobs only, in route order, with the address and the customer's phone number as tap targets. The tech taps a job and gets one screen: the scope, the gate code, the parts list, and a checklist. Each checklist item is a tap to complete. Status is a row of big buttons: On my way, Arrived, Done, Needs a return visit. Tapping a button stamps the time and the location on the job. Photos upload from the camera straight onto the job, with the time attached. The customer signs on the screen and the signature is stored on the job. If the truck has no signal, the app keeps the tech's taps in a queue and sends them when signal returns. The dispatcher sees each status change within seconds of the tap. That is a short list. The big field platforms add routing, fleet tracking, and driver scorecards a crew of eight will never open. A crew of eight needs the short list, shaped to its own spreadsheet. We describe the full version of that build on the [field service apps](https://llamapress.ai/field-services) page. ## How does the spreadsheet map to phone screens? Every tab and column in your spreadsheet already has a place in the app. That mapping is why the build is fast. The Jobs tab becomes the job list. Each row in the Jobs tab becomes one job detail screen. The Customer, Address, and Phone columns move to the top of that screen as tap targets. The ten checklist columns (Safety check, Parts on truck, Photos taken, and so on) become tap-to-complete items. The Status column with its dropdown of five values becomes five buttons, and the app records who pressed which button and when. The Notes column becomes a timeline. In the spreadsheet, that cell holds "8/14 called cust, 8/15 no answer, 8/16 done" typed by three people. In the app, each note has an author and a time. The Photos column becomes a gallery on the job. The Tech column becomes a login, so each tech sees only their own jobs. We cover that part in [adding logins and permissions to a spreadsheet process](https://llamapress.ai/how-to-add-user-logins-and-permissions-to-a-spreadsheet-based-process). The Customers tab and the Price List tab become their own records too. The office edits prices in one place and the job screen reads from there. If your spreadsheet is also your estimating tool, see how we handle the pricing tabs in [custom estimating software built from your spreadsheet](https://llamapress.ai/custom-estimating-software-built-from-the-spreadsheet-you-already-have). ![Field worker in an orange safety vest writing job notes on paper outdoors, the paperwork a phone app replaces](https://images.unsplash.com/photo-1770822662831-c361f15790ea?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w4NTU2MDF8MHwxfHNlYXJjaHwyfHx0ZWNobmljaWFuJTIwdXNpbmclMjBwaG9uZSUyMG9uJTIwam9iJTIwc2l0ZXxlbnwwfHx8fDE3ODgzNjE4ODl8MA&ixlib=rb-4.1.0&q=80&w=1080) Photo by [Agustín Pimentel](https://unsplash.com/@agustin_pimentel?utm_source=leonardo_rails_app&utm_medium=referral) on [Unsplash](https://unsplash.com/photos/man-in-orange-vest-writing-on-paper-outdoors-ecv_knkA24w?utm_source=leonardo_rails_app&utm_medium=referral) ## What are the three ways to get there? You can lay a no-code builder over the sheet or hire an agency to build a native app. Or you can have an AI agent build a web app from the spreadsheet. Prices in the table are list prices as of this writing. | | AppSheet or Glide over the sheet | Native app from an agency | AI-built web app (LlamaPress) | | --- | --- | --- | --- | | Price | AppSheet $5, $10, or $20 per user per month. GlideOS $25, $50, or $125 a month by team members and credits | Typical quotes $40,000 to $250,000 up front, then maintenance | Hosted from $9.99 a month, no per-user fee. Built for you from $2,000 | | Where the data lives | The sheet stays the database. Glide caps spreadsheet sources at 25,000 rows | The agency's database, on the agency's terms | A PostgreSQL database you own, with the spreadsheet history imported | | Screens | List and form views generated from the columns. Limited layout control | Fully custom, designed in workshops | Custom job screens built from your tabs, changed in plain English | | Photos, signature, offline | AppSheet runs offline with background sync on all plans. Photos and signatures supported | All possible, each one scoped and billed | Photos and signatures on the job record. Offline queue built in when your crews need it | | Per-tech logins and roles | AppSheet roles start on the $10 Core plan. GlideOS org roles on the $125 Pro plan | Included in the build | Included. Tech, dispatcher, and office roles from day one | | Time to first version | A day or two for a list and form | Three to nine months | First working version within days. The RSB rebuild shipped in six weeks | | Who owns the code | The vendor. No code export on AppSheet. Glide shows code only on Enterprise | Depends on the contract. Ask | You. Standard Ruby on Rails code in your own GitHub account | Sources for the table: the [AppSheet pricing page](https://about.appsheet.com/pricing/), the [GlideOS pricing page](https://www.glideapps.com/pricing), Glide's data-source docs, and our own [pricing](https://llamapress.ai/pricing) and [services](https://llamapress.ai/services) pages. Agency figures are typical quotes we hear from operators, so treat that band as a range. Glide's documentation also states that syncing with an Excel file requires a Business or Enterprise plan. For a wider look at every tool in this category, read [the best Excel to web app converters compared](https://llamapress.ai/the-best-excel-to-web-app-converters-in-2026-compared-honestly). AppSheet deserves a fair word. If your spreadsheet already lives in Google Sheets and you want a list plus a form by Friday, AppSheet is a good answer. Google lets you test with up to 10 users at no cost. The limits show up later. The sheet stays the database, so two techs editing the same job still collide. A 40-column row becomes a 40-field form. And the per-user meter grows with every hire. ## When is the Excel mobile app enough? The Excel mobile app is enough when one tech reads the spreadsheet and never writes to it. A solo plumber who keeps a price list in Excel can open the file on a phone, search a name, and call the number. Nothing needs to sync back. The same goes for a read-only parts lookup that the office updates once a month. Keep those in Excel. The line is crossed when a second person writes to the file from the field. Two writers on a whole-file save produce lost edits, and lost edits in a job list mean missed visits and unbilled work. ## How do you roll a field app out without a revolt? Give the app to two techs first, for one week, and leave the spreadsheet running beside it. Pick one tech who likes new tools and one who hates them. The second one is your real tester. Every evening, ask both techs what annoyed them that day. You will hear the same three things: a button in the wrong place, a field nobody uses, and a step that takes two taps too many. Fix those three and leave everything else alone. Small fixes in the first week decide whether the crew uses the app or ignores it. On day eight, compare the app's job records against the spreadsheet for that week. If the app has every status change, photo, and signature, retire the spreadsheet for the field. The office can keep a read-only export for a month, then stop opening it. ## How the spreadsheet becomes the app You [upload the spreadsheet](https://llamapress.ai/excel-to-app) that runs your field work, tabs and color coding included. Leonardo reads the Jobs tab as the job table and the column headers as the fields. The Status dropdown becomes the buttons, the Tech column becomes the logins, and the checklist columns become the tap-to-complete items. Leonardo then builds a Ruby on Rails app on a PostgreSQL database, with a phone layout for techs and a desktop layout for the dispatcher. The code lands in your own GitHub account. You then change the app by describing the change. "Add a Needs a Return Visit button that emails the office." "Hide the price fields from techs." A human engineer reviews each build before you rely on it. Hosted plans start at $9.99 a month with no per-user fee, and a done-for-you build sprint starts at $2,000, as of this writing. The steel contractor RSB went from an estimating spreadsheet to a deployed app in six weeks. A field job list is a simpler spreadsheet than that one, and most crews are on the phone version within days of the first [upload](https://llamapress.ai/excel-to-app). From Spreadsheet to Phone App ### Give your techs one job per screen. Upload the job list spreadsheet your office keeps today. Leonardo turns it into a phone app with status buttons, photos, and signatures, on a database you own. [Build My Field App](https://llamapress.ai/excel-to-app) [See Field Service Apps](https://llamapress.ai/field-services) Prefer to talk first? [Contact us](https://llamapress.ai/contact) and we will look at your workbook with you. ## Frequently Asked Questions ### How do I turn my Excel spreadsheet into something my field team can use on their phones? Pick one of three routes. Open the spreadsheet in the Excel mobile app if one tech only reads it. Lay Google AppSheet or Glide over the sheet if you want a list and a form fast and accept per-user pricing. Upload the spreadsheet to LlamaPress if you want custom job screens, photos, signatures, and logins on a database you own, with no per-user fee. ### Can my field team use Excel on their phones? A field team can open an Excel spreadsheet on a phone, but editing it there is painful and risky. The Excel mobile app shows a few columns at a time, saves the whole file, and requires a Microsoft 365 subscription for advanced editing of business files. Two techs editing the same file from trucks with poor signal will overwrite each other. Reading is fine, and writing from the field is where Excel breaks. ### Do I need an app store app or is a web app enough? A web app is enough for almost every field crew. A web app opens in the phone's browser, can be added to the home screen with its own icon, and uses the camera for photos. A web app also skips app store review, so a fix ships in minutes. An app store app only earns its extra cost when you need deep hardware access such as Bluetooth scanners. ### Can a field app work offline? A field app can work offline when offline support is built in. The app stores today's jobs on the phone and keeps each tap in a queue until signal returns. AppSheet includes offline with background sync on all plans. A LlamaPress web app gets an offline queue when your crews need one, so tell us where your trucks lose signal before the build starts. ### How do photos get attached to a job? In a field app, the tech taps a camera button on the job screen and takes the photo. The photo saves onto that job with a time stamp. The office sees the photo on the same job record seconds later. In a spreadsheet, the photo sits in the camera roll and the cell holds a filename someone typed. Tying the photo to the job is the single feature crews notice first. ### How much does a field service app cost? As of September 2026, Google AppSheet costs $5 to $20 per user per month. GlideOS costs $25 to $125 a month by team size and credits. A LlamaPress web app built from your spreadsheet is hosted from $9.99 a month with no per-user fee, or built for you from $2,000. Agency quotes for a native field app typically run $40,000 to $250,000 over three to nine months.