Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

Your government grant paid for an MVP. Here is what the stamped quote must cover.

A founder I spoke with this week had good news: her reptile-monitoring startup was selected for a Korean government support program. The program covers up to 8 million won of MVP development, paid to a vendor she chooses

A founder I spoke with this week had good news: her reptile-monitoring startup was selected for a Korean government support program. The program covers up to 8 million won of MVP development, paid to a vendor she chooses, on one condition. The invoice has to be stamped by the company that will actually build it.

That condition is where most of these projects quietly go wrong.

Not the technology. The paperwork. The quote is the specification: what the operating agency approves is what gets paid, and what gets paid is the only scope anyone is willing to revisit later.

If you are holding an approval letter and a deadline, here is what I would settle before you ask a builder to put a seal on a number.

1. The quote is a scope, not a price

A one-line quote, "MVP development, 8,000,000 KRW", reads as a favour and behaves like a trap. Six weeks in, somebody has to decide whether push notifications were included, and nobody can point at a sentence.

Write the line items so a stranger can check them:

  • Customer app: onboarding, core record entry, history view
  • Admin view (one operator is enough at this stage)
  • Notifications: which events, which channel
  • Store registration and review support for iOS and Android
  • Server setup, deployment, handover
  • Warranty period and what it covers

If a builder cannot break 8 million won into five lines, they have not thought about the build yet.

2. VAT and payment timing are not small print

Korean quotes usually read "6,500,000 KRW (VAT excluded)". A grant of 8 million with VAT on top lands at 7,150,000. That is fine here, and awkward when the grant is 5 million. Decide early whether your budget absorbs VAT.

Then ask when the program actually pays. Most pay after completion and after a result report, which means your builder is financing the build. Say that out loud during negotiation. A builder who knows it prices the wait in. A builder who does not will discover it in week five, usually with a pause in work attached.

3. Who owns the accounts

Store developer accounts, the database, the domain, the payment merchant account. Under a grant, the result usually has to belong to the funded company.

Put it in writing that every account is created in the company's name from day one and the builder works as a guest, not as the owner. Moving a live app off someone else's Play Console later is a week of paperwork nobody budgeted for, and a store transfer can stall a release that the deadline will not wait for.

4. Store review belongs in the schedule

I have watched a finished app sit for six days waiting on Apple, and a first submission come back over a privacy manifest missing a single line.

If the report deadline is fixed, the submission date is not the delivery date. It is delivery minus at least five working days, plus one rejection cycle. Build that into the quote. Not "three weeks if everything goes well", but "three weeks including one review round".

5. Three answers that move a price by 30%

From the founder's side, these change the build more than any feature list:

  1. Does it need to run on both iOS and Android, or is one enough for the first round?
  2. Is there existing data, a spreadsheet or an old app, that has to come across?
  3. Who signs off, and what does done mean: a working app in a store, or a demo video and screens?

A builder who does not ask these three is quoting a template. You will pay for the template difference at the end, in the part of the project where nobody is cheerful anymore.

6. What I would cut first

Grants tempt scope. Every feature sounds fundable, and the reviewer's eyes are on the plan, not on the build.

Cut in this order:

  • Camera and AI features that need hardware you do not have yet
  • Multi-language before the first paying user
  • Social login as a requirement rather than an option
  • Reporting dashboards before there is data worth reporting

The founder above had a smart-camera product in her plan. The grant covers the record-keeping app: register an animal, log its weight, shedding, feeding, look back at the history. No camera. That is the right cut. What ships is what gets reported, and the camera can be the next round.

7. A checklist before the seal goes on

  • Scope split into 5 to 8 line items, each verifiable
  • Amount, VAT treatment, and payment milestones
  • Delivery date with the store review window named
  • Warranty period and response time
  • Source code and database schema handed over at completion
  • Accounts in the funded company's name
  • What happens if the agency asks for a revised quote

Two pages. If a builder balks at two pages, that is the answer to a different question.

I build small web and app MVPs, usually three to five days for a scoped slice and about three weeks for something that has to survive a store review. Studio page: https://cpcai-studio.netlify.app/en/ — questions: [email protected]

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.