Web apps
A web app, live in about a week.
One core workflow, done properly: accounts, roles, payments where you need them, an admin view, and the monitoring and backups most first versions skip. Launched on your domain, in your accounts.
Prefer to write? Send your requirements
In short
PutThrough builds web apps — client portals, SaaS MVPs, booking and scheduling systems, marketplaces and member dashboards — in about a week, at a fixed price agreed in writing after a free scoping call. Each one launches on your own domain with sign-in and roles, Stripe payments where you need them, an admin view, error monitoring and tested backups, and you own the code and every account from the first commit.
01Who it’s for
For a first version that real customers will use.
-
Founders with a product to test
You need paying users on something real, not a prototype that has to be rebuilt before anyone trusts it with their data.
-
Businesses with a customer-facing process
Bookings, orders or client work handled by email and spreadsheets, and ready to become a portal your customers log in to.
-
Teams replacing a fragile prototype
A no-code or AI-built version proved the idea. Now it needs to be something you can safely grow.
02Example uses
What a one-week web app usually is.
-
Client portals
Customers log in to see their projects, documents, invoices or orders, and do the few things they currently email you about.
-
SaaS MVPs
The one workflow your product is really about, with sign-up, plans and billing around it.
-
Booking and scheduling systems
Availability, bookings, deposits or payments, reminders, and a calendar view for your staff.
-
Marketplaces
Two sides, listings, and a transaction between them, kept to the flows that matter for launch.
-
Member dashboards
Gated content, account settings and a subscription, with an admin view of who has access to what.
03What fits in a week
One product, one core workflow, done properly.
Fits in a week
- Sign-up and sign-in, including Google
- Team roles and permissions
- Stripe payments or subscriptions
- An admin view for your team
- Two or three integrations you already use
- Transactional email
Needs longer, or a call first
- Several separate products at once
- Real-time collaboration on shared documents
- Large migrations out of a legacy system
- Formal compliance programs such as HIPAA or SOC 2
04A sample week
Seven days, one web app.
The same seven days as every build, with this product’s work in them. Your week is planned on the scoping call.
- Day 0
Scoping call and fixed quote
We cut the idea down to the workflow that matters, and write down what is in and what waits for week two.
- Day 1
Data model and screens
Who the users are, what each role can see and do, the tables behind it, and the screens, agreed in writing.
- Days 2–5
Build, in the open
Accounts and roles first, then the core workflow, payments and the admin view. A preview link and a written update every evening.
- Day 6
Harden
Access rules tested per role, payment webhooks verified, error states handled, a backup restored, monitoring switched on.
- Day 7
Launch and handover
Production deploy on your domain, then the written handover and a recorded walkthrough.
05What you get
What you walk away with.
- The web app, live on your domain
- Access rules tested for every role
- Stripe set up in your account, with verified webhooks
- Error monitoring and uptime checks switched on
- Automated backups, with a restore already tested
Plus the standard handover every build ends with: source code, a written handover, a recorded walkthrough and every account in your name. The full Day 7 list
06Stack
Proven, widely supported defaults.
Chosen so the next engineer can pick it up without us. If you have a strong reason for something else, tell us on the call.
- Language
- TypeScript
- App
- React and Next.js
- Data and auth
- Postgres, usually through Supabase
- Payments
- Stripe
- Hosting
- In your own account
07Pricing
A fixed price for a fixed scope.
Your exact price is fixed in writing after the scoping call, before you commit to anything.
After launch, the care plan is from $499 per month.
Prefer to write? Send your requirements
08Questions
01 Can it handle more users later?
Yes. The defaults we use run products far larger than a first version. What usually needs work as you grow is the product itself, not the foundations, and the handover notes where the limits are.
02 Can we add features after launch?
Yes. You can add them yourself, hire anyone, or book another week with us. Anything that didn’t fit in the first week goes on a written list, so nothing is lost.
03 Do you design the screens?
Yes, simply and cleanly, on Day 1, agreed with you before we build. If you have Figma designs, we work from those instead.
04 Where is it hosted?
In accounts in your name, so the product and its bills are yours from the start. We set them up with you in the first days of the week.