Small enough to finish

How to Build a Small Business App on a Limited Budget: One Workflow, One User

Say you have $1,000, a free Tuesday and an app idea. You cannot afford the app you are picturing. You can probably afford the one that matters, once you shrink it to one job for one person. That person is very often you, at 10 p.m., with a stack of receipts.

November 15, 2026 · 9 min read

acmepoolcare.com · first app question
The conversation before the quote
$1,000, one pool route and an app idea
I have about $1,000. Can I have an app?
Not a native one from us. Those start at $3,750. A web app starts at $575, depending on complexity.
What would I even put in it?
One job. Today's stops, the readings, send the email. Three screens, and you are the only user.
Could I try that for free first?
Yes. A form and a shared sheet, saved to your phone, for a month.
Illustrative: a sample conversation for a fictional solo pool cleaner

The short answer

Build the smallest thing first: one workflow, used by one person, in a browser. Prove it free with a form and a shared sheet. Then buy a web app, which starts at $575 with DataCram, depending on complexity. Connect your other tools only once it is in daily use. Pay for a native app, from $3,750, only after people use the cheaper version every week.

On this page
  1. Why one user beats a thousand imaginary ones
  2. What each budget actually buys
  3. Rung one: fake it for a month with free tools
  4. Rung two: a made-up pool cleaner's three-screen web app
  5. The monthly lines a small web app actually carries
  6. Things to refuse while the budget is small
  7. How to know you have earned the next rung

Why one user beats a thousand imaginary ones

The app in your head has customers. Customers need accounts, password resets, a privacy policy, a support address and a reason to install. All of that costs money before anyone has done a single useful thing with your software. Start with you instead. You need no convincing and no training. You will forgive an ugly screen. And you will report bugs quickly, in strong language, to someone who can fix them.

A workflow has a beginning, an end and one person responsible. "Log the readings at each stop and email the customer" is a workflow. "Run my business" is not, and neither is "customer engagement." If you cannot describe yours on an index card, you have no budget problem yet. You have a definition problem, and a developer will happily charge you to discover that together. If you want a stronger filter, the test for needing an app comes first.

What each budget actually buys

These prices are as of November 2026. DataCram's are from our pricing page. Where the budget does not reach us, we say so and give you the route that works without us, because a useful page beats a sales page that dead-ends at a form.

An app budget ladder for a one-person or very small company
What you can doWhat you cannot do yet
$0A form, a shared sheet and a saved link. HubSpot's free CRM (up to two users and 1,000 contacts). Zapier's Free plan (100 tasks a month).Anything with your own logic or your own login
Under $575No build from us at this level. Rent instead: Zapier Professional at $19.99 a month billed annually or $29.99 monthly, and a real Workspace account at $7 per user per month (confirm the term at checkout).Software you own
$575 to $1,500One web app, portal or integration, from $575 each, depending on complexitySeveral workflows at once, or an App Store listing
$1,500If you have no decent site, a site up to 10 pages, with booking, lead capture and one API integration included. That may beat any app.A native app
$3,750 and upA native iOS or Android app, from $3,750, if the earlier rungs proved the demandBoth platforms at the floor price. A second platform is more scope.

Financing can stretch the same dollars but not the scope. We offer 0% with 25% down for up to 12 months on web applications: $575 comes to $143.75 down and about $35.94 a month. On iPhone builds, $3,750 comes to $937.50 down and about $234.38 a month. No special small-company price exists. We would rather show you a smaller project than a smaller number that later turns out to be false.

Rung one: fake it for a month with free tools

Before you pay for anything, build the embarrassing version. It teaches you what the software has to do, and sometimes it reveals that the embarrassing version is good enough. In that case, we have just cost ourselves a project and saved you some money. That is a fine outcome. An owner who wants to go deeper can read why a spreadsheet works until it does not.

  1. 1

    Write the workflow on an index card

    Who starts it, what they enter, what comes out and where it goes. Keep it to one side of the card.

  2. 2

    Build a form and a sheet

    Any free form tool feeding a spreadsheet. Save the form's link to your phone's Home Screen. You now have what looks suspiciously like an app.

  3. 3

    Automate one step, if any

    A free Zapier account lets a new row send an email. At 100 tasks a month, you will find out quickly whether you have a real volume problem.

  4. 4

    Use it every day for a month

    Keep a list of what annoys you. That list is the first draft of your specification, and it is worth more than any wireframe.

  5. 5

    Put a number on it

    How many minutes does it take now, and how many would it save? The automation savings calculator turns that into dollars. Timing the task gives you the minutes.

Rung two: a made-up pool cleaner's three-screen web app

Say a solo pool cleaner in Mesa, invented for this example, spends her evenings typing chemical readings into emails. Her month of forms proved the workflow. She has 40 stops a week, and she is tired of it. This is what a tight scope for a first web app looks like. It is an illustration, not a quote, and the price would depend on complexity.

Screen one: today

A list of today's stops in route order. Tap one to open it. No map, because her phone already has one and it is free.

Screen two: readings

Four number fields, a notes box and a photo. A big button says Send. She uses it standing by a pool with wet hands.

Screen three: done

A confirmation, the email that went out, and the next stop. That is the whole application.

What she left out

Customer logins, invoicing, an admin dashboard, a chatbot and anything that had to be explained. Each is a later decision with a later price.

Warm shallow-focus photo of a pool test kit, a skimmer handle and a phone on a tailgate, one cuffed hand at the edge, no faces
The whole first version has to work out here, by one tired person, with wet hands.

Nothing on that list needs the App Store. It opens from a link, and on iPhones it can sit on the Home Screen with its own icon: MDN's guide says iOS 16.4 and later can install web apps from the Share menu. Her Apple fee is zero. Native against web has the rest of the differences. For more on what a first build costs and what moves it, read the web app cost page.

The monthly lines a small web app actually carries

A web app needs somewhere to live. Ask whoever builds yours to name that line, and write it into the quote. Here are public prices for two popular hosts, as of November 2026, so you can see the scale. Your app may use something else, and neither of these is a recommendation for every case.

Our website hosting and maintenance plan, starting at $55 a month, is for websites. Whether and how it covers a given web app is a question to ask on the quote, not something to assume. Cheap to run is the whole reason to pick this path. A monthly bill you never see coming is how a small project stops being cheap.

Things to refuse while the budget is small

You will be tempted. Vendors will help. Some of these are good ideas for later, and some are just stickers. Say no to all of them for now, and write them on the Later list, which costs nothing to maintain.

Refuse for now

  • An "AI-powered" anything, unless you can say what it does on a given Tuesday
  • A separate admin panel, when a spreadsheet export will do
  • Customer logins, until a customer has asked
  • A second platform, a dark mode or a logo animation
  • A monthly retainer for an app with one user

Pay for anyway

  • Backups, and one test of restoring them
  • A separate login per person
  • Your name on every account, including code and hosting
  • A written scope with a fixed price
  • A real security approach for any customer data
The Later list is the cheapest software you will ever own, and it never goes down.

How to know you have earned the next rung

Move up only when the current rung complains. Not when you are bored of it, and not when a salesperson says it is time. If a helper joins and needs the same tool, add a second login. If a customer asks for the same data, consider a customer portal. If you are retyping between systems, a same-day integration is the next purchase. Each is a small buy with a clear reason.

A native app is the top rung. It is worth a look if people use your web version every week, if a real test shows the browser cannot do the job, and if you have read the whole iPhone bill. Scope cuts that survive will help hold down that price, and our iOS guide for small companies explains the rest. Plenty of owners will never get there, and they will be right. If your idea wants to grow up, from idea to working web application maps the stages.

The section home has the broader case for owning small pieces of technology. If you want a second opinion on your index card, call (210) 346-0848 or send it in. DataCram has been building for the web since 1999, and we built and still run our own software, including Athena CMS. We can tell you whether your card describes a $575 job, a $3,750 job or a free Saturday.

Questions owner-operators ask

Free tools first: a form feeding a spreadsheet, saved to your phone's Home Screen. Use it for a month. If it holds, you may be done. If it does not, a web app with DataCram starts at $575, depending on complexity, with no Apple fee, and it runs on iPhone and Android from one build. Native apps start at $3,750.

Often, if it stays to one workflow. A web app, portal or integration starts at $575, depending on complexity, and a simple one-person tool may sit near that floor. Add a monthly hosting line, which your builder should name in the quote. It will not include customer accounts, a dashboard and a second platform. If your idea needs those on day one, it is a bigger project than your budget.

Do the work by hand for a month and write down what annoys you. Then set up a free form and a shared sheet. HubSpot's free CRM and Zapier's Free plan, with 100 tasks a month, as of November 2026, can carry a surprising amount of a very small operation. Come back when a specific step is costing you more than a build would.

You remove most of the cost and most of the risk. No account system, no support, no persuading anyone to install anything, and no App Review. You also get daily feedback from someone who understands the job. Once it works for you, adding a helper is a small step. Adding customers is a larger one, and now you will know whether it is worth paying for.

Yes. DataCram offers 0% financing with 25% down, up to 12 months. A $575 web app works out to $143.75 down and about $35.94 a month, and a higher quote scales the same way. Financing does not change the scope, so we would still shrink the project first. Paying less overall usually beats paying the same amount more slowly.

Keep a written scope, a fixed price and a Later list. Ask what each new feature costs before saying yes, and buy one rung at a time. Own your code and accounts so you can move if the relationship sours. Most small projects grow expensive through a series of reasonable little additions, not through one big mistake, so make every addition earn its way in.

Keep reading

Free · No obligation

Send us your index card

Write down the one job, who does it and what it takes now. A person at DataCram replies with what the smallest working version would be, whether it fits your budget, and what to try for free if it does not.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote