Skip to content
Metzger Creative
Services

Web applications

The first version real users can pay for, built so the second version does not start over.

Book 20 minutesSee the other services

Who this is for

  • You have validated the problem and need the product built properly
  • You have a prototype that got you here and will not get you further
  • You are replacing a spreadsheet that is now load-bearing for your business
  • An agency built v1 and left you with something nobody can maintain

What gets built

The grid goes down first, then everything that sits on it. Same order this site was built in.

How it works

  1. Scope written down together, including what is explicitly not in v1

  2. Architecture decisions made with you, with the tradeoffs named

  3. Weekly deploys to something you can click, from the first week

  4. Tests on the paths that cost money when they break, not a coverage percentage

  5. Handover: documented architecture, a runbook, and a codebase another engineer can pick up

What it costs

The bands that apply to this work, with what each one includes and what pushes it up or down. Nothing here is a number you have to book a call to hear.

Web app MVP

The first version real users can pay for, built so the second version does not start over.

$25K–$75K

What it includes

  • Product and architecture decisions made with you, not presented to you
  • Auth, billing and the admin surfaces every app needs and nobody scopes
  • Automated tests on the paths that cost money when they break
  • Deploy pipeline, monitoring and a runbook you keep

What moves the number

  • How many user roles and distinct workflows ship in v1
  • Third-party integrations, especially payments and anything with a certification process
  • Whether you need multi-tenancy on day one
  • Compliance requirements: SOC 2, HIPAA, PCI

Technical audit

A senior read of what you already have, and a straight list of what to do about it.

$5K–$12K

What it includes

  • A written report you can hand to an investor, a board or a new hire
  • Architecture, data model and infrastructure review
  • Security and dependency risk, ranked by what would actually hurt you
  • A prioritized remediation plan with rough effort against each item

What moves the number

  • How many services and repositories are in scope
  • Whether infrastructure and CI are included or just application code
  • Whether you want a prioritized remediation plan or findings only

It stands on its own, and the fee comes off the first build engagement that follows.

Questions people actually ask

What stack do you build on?
TypeScript end to end, React and Next.js on the front, Postgres behind it, deployed to AWS. Boring on purpose: the goal is that your next hire already knows it.
Can you take over an existing codebase?
Usually, and the audit is the right way to start. It tells you and me whether the thing is worth continuing or worth replacing, before either side has committed to a build.
What happens after launch?
Either you take it in house, which is a clean handover I plan for from the start, or you move onto a care plan. Both are fine by me. Being quietly indispensable is not a business model I want.

Sound like your situation?

Twenty minutes, no deck, and a straight answer at the end about whether this is the right piece of work for you. If it is not, I would rather say so now than at proposal stage.

Book 20 minutesSee every band