Free template · software proposal

Software development proposal template

A proposal from a developer to a client for building an app, written out in full: the problem in the client's words, how you'll work, the stack and why, a phased price with optional extras, payments and terms. It's a services proposal, not a startup pitch deck.

Sections
11
Estimate
11 lines, 170 hours
Example total
$20,570.00
Payments
40% / 20% / 40%
Proposal

Fieldnote: field reports app, design and build

Prepared for Fieldnote

Investment
From $20,570
Payments
3 stages

What you need

Your field teams write site visits on paper and retype them at the office, so reports reach clients days late and photos get lost. You want one app where a visit is recorded on a phone, on site, even without signal, and shared with the client the same day.

We propose to design and build that app in three phases over 8 weeks, with a working demo every Friday so you see progress, not promises.

How we'll work

  1. Discovery and design (2 weeks). A workshop with your field leads, wireframes for every screen, and a clickable prototype you approve before any code is written.
  2. Build (4 weeks). Weekly releases to a staging link you can try on your own phone. Each Friday: a short demo and a written note of what's done and what's next.
  3. Test and launch (2 weeks). Testing on real devices, fixes, launch on your domain, and a handover so your team can run it without us.

Tech stack, and why

  • Next.js and TypeScript: one codebase for the app and its pages, fast on phones, and easy to hire for later
  • Postgres (via Supabase): your data is relational (teams, sites, visits); you also get sign-in and row-level security, so each team only ever sees its own visits
  • Offline storage in the browser, synced when the signal returns, so a basement site visit is never lost
  • Stripe for subscriptions and invoices
  • Vercel hosting, with a preview link for every change
  • Sentry error alerts, so problems reach us before your users do

What you get

Discovery and design

  • Product brief from the workshopS-1
  • Wireframes and a clickable prototypeS-2
  • A small design system in FigmaS-3

Build

  • Sign-in, teams and rolesS-4
  • Site visits with notes, photos and locationS-5
  • Offline drafts with syncS-6
  • Search and filtersS-7
  • Client-ready reports (link and PDF)S-8
  • Stripe subscriptions with a free trialS-9

Launch

  • Production launch on your domainS-10
  • Monitoring and error alertsS-11
  • Handover documents and a recorded walkthroughS-12

Not included

  • Native app-store appsX-1
  • Single sign-onX-2
  • Data migration from another systemX-3
  • CopywritingX-4

Investment

Priced by phase. The two extras at the end are optional: tick them if you want them and the total updates. A 10% contingency covers the unknowns and is only invoiced if used.

TaskHoursRateAmount
Discovery and design · 34 h$3,740.00
Discovery workshop and brief6$110.00$660.00
Wireframes and prototype16$110.00$1,760.00
Design system12$110.00$1,320.00
Build · 108 h$11,880.00
Sign-in, teams and roles18$110.00$1,980.00
Site visits, photos and location30$110.00$3,300.00
Offline drafts and sync20$110.00$2,200.00
Search and filters10$110.00$1,100.00
Client-ready reports14$110.00$1,540.00
Stripe subscriptions16$110.00$1,760.00
Launch · 28 h$3,080.00
Device testing and fixes16$110.00$1,760.00
Launch, monitoring and handover12$110.00$1,320.00
Optional extras
Admin dashboard for your team16$110.00+$1,760.00
Usage analytics for your clients' reports12$110.00+$1,320.00
Subtotal$18,700.00
Contingency (10%)$1,870.00
Total$20,570.00

Payments

  1. To startOn approval$8,228.0040%
  2. Design approvedEnd of week 2$4,114.0020%
  3. LaunchWeek 8$8,228.0040%

Assumptions and exclusions

  • You provide access to your domain, Stripe and email sender in week 1, and one person to approve each phase
  • Hosting and services (about $40–80 a month at launch) are billed to your accounts
  • Not included: native app-store apps, single sign-on, data migration from another system, copywriting

Questions you might have

Why price by phase rather than by the hour?

You know the cost of each phase before it starts, and you can stop after any phase and keep everything built so far.

What if we want changes along the way?

Send them in writing. Within 2 business days you get the effect on cost and dates; nothing extra is billed without your yes, and the agreed change becomes a new version of this proposal.

Who owns the code?

You do, from final payment. The repository lives in your GitHub organisation from day one.

About us

[Two lines about you or your studio, and one similar project you've shipped, with a link.]

Terms

Invoices are due within 14 days. Work outside the agreed scope is quoted in writing before it starts. Ownership of the code and designs passes to you on final payment. We fix defects against the agreed scope free for 30 days after launch. Either side can stop with 10 days' notice; you pay for work done and keep it.

Next step

Approve below to lock in this scope and price. We'll send the deposit invoice and book the kickoff workshop for the following week.

A worked example for a fictional client. Every word and number is yours to change.

How to write each part

  1. Open with their problem, in their words

    The first paragraph should make the client think “yes, that's exactly it”. Describe what's going wrong today and what changes when it's fixed. Your company history can wait until the end.

  2. Show how you'll work, in phases

    Clients buy predictability. Phases with a visible checkpoint (a prototype to approve, a staging link every Friday) tell them what a week with you looks like, and give you natural points to invoice.

  3. Name the stack, with one reason each

    Non-technical buyers don't need the details, but they do need to trust the choice. One plain reason per tool (“each team only ever sees its own visits”) does more than a list of logos. Technical buyers will check it, so be specific.

  4. Price by phase, with extras the client can choose

    A line per piece of work shows where the money goes. Put nice-to-haves in an “optional extras” group: the client ticks what they want and sees the total change. In Devposal the client ticks extras on the proposal itself, and the choice is locked into what they sign.

    Keep contingency as its own visible line rather than padding every estimate.

  5. Tie payments to milestones

    A deposit to start (30–50% on small projects), then payments at checkpoints the client can see: design approved, staging signed off, launch. Each payment matches something delivered, which makes invoices easy to approve.

  6. Answer the objections before they're raised

    Three or four short questions and answers (why fixed price, what if we change our minds, who owns the code) handle the hesitation that otherwise turns into a week of email.

  7. Sending it from the UK

    UK contractors usually quote a day rate; project work is often a fixed price built from days, so show the days behind each phase. If you're VAT registered, show VAT at 20% as its own line, or say “prices exclude VAT” under the total, and put your VAT number on the proposal. For business clients abroad there's usually no UK VAT to add.

    The UK day rate calculator works out the rate after income tax and National Insurance, and the VAT guide covers the threshold and clients abroad.

  8. End with one clear next step

    Tell them exactly what happens when they say yes: an invoice, a kickoff call, a start date. Then make saying yes one click. A link they can approve on their phone beats a PDF they have to print and sign.

Questions people ask

How do you write a software development proposal?

Start with the client's problem and the outcome, then your approach in phases, the tech stack with a reason for each choice, what's included, a phased price, the payment schedule, assumptions and exclusions, terms, and one next step. The example above follows exactly that order.

What should a software proposal include?

The problem and goal, scope (deliverables), approach and timeline, the tech stack, a line-by-line estimate, the payment schedule, assumptions and exclusions, terms (ownership, changes, warranty), and how to approve. Optional extras and a short FAQ help the client decide faster.

Should I quote a fixed price or bill hourly?

Fixed price per phase suits clear scopes and clients who need a budget; hourly suits vague or changing work. A common middle path is a fixed-price discovery phase first, then a fixed price for the build once the scope is clear.

How much padding should I add to an estimate?

Developers report anything from 1.25× to 4× in practice. A visible 10–20% contingency line is easier to explain than hidden padding, and a “likely between” range is honest when scope is still moving.

How should a proposal handle change requests and scope creep?

Say it up front: changes come in writing, you reply with the cost and date impact, and nothing extra is billed without approval. Then send approved changes as a new version of the proposal so everyone signs the same current scope.

Is there a free software proposal template I can download?

Yes: the full template above can be downloaded as Markdown (which pastes cleanly into Google Docs, Notion or Word) or saved as a PDF with your browser's print. Or open it in Devposal to edit it and send it as a link your client can approve.

Related