Prototype to production
We take what you have, whether a freelancer built it or you built it yourself with AI coding tools, and add what production needs.
Logins and roles, each customer’s data kept apart, billing, monitoring, and evals for the AI parts. The audit decides what we keep and what we rebuild.
- Build
- 4–8 weeks
- Starts with
- A one-week audit, then a one-week blueprint
- Build price
- Fixed in writing before code
- Every week
- A working build you can click
- The code
- Yours
Who it’s for
Build engagements fit best when there’s a real product or workflow with users behind it.
A good call when
- You have a working prototype, whether it came from AI coding tools, a freelancer or another team.
- Someone is about to depend on it: a pilot customer, a second account, a first invoice.
- There’s a date attached, and you want to know the build price before the code.
- You want it built so an in-house hire can own it later.
Not the right fit when
- You’re still finding out whether anyone wants it. Keep building with the AI tools: they’re good at exactly that stage.
- Scope will keep moving and you’d rather pay for time. An hourly dev shop is the better call.
Not sure which kind of build you need? Start with the audit
What’s included
What a prototype usually lacks is everything a second customer, a real payment or a security review will test.
Logins and roles
Who can sign in, and what each person is allowed to see and change.
Each customer’s data kept apart
One customer’s records never show up in another customer’s account.
Billing
Your customers pay inside the product, on the plans you set.
Monitoring
You see when something fails in production, and where.
Evals for the AI parts
Tests that check the model’s output against known-good answers, so you know when it’s wrong.
Keep or rebuild
The audit goes through what exists and decides, part by part, what stays and what gets rebuilt.
Your prototype
The screens and the flow your users already know.
audited: keep or rebuild
Added for production
- 01Logins and roles
- 02Each customer’s data kept apart
- 03Billing
- 04Monitoring
- 05Evals for the AI parts
The production checklist
Everything a real customer, a real payment or a security review will test, in six groups. In the audit week we go through all 48 against what you have, and mark each one: already there, needed before launch, or fine to wait.
Product
- Your demo
- Onboarding
- Admin panel
- Email delivery
- Notifications
- Accessibility
- Translations
- Right-to-left
Your demo, and everything a new user meets around it, in their language, right-to-left included.
Access
- Sign-up
- Login
- SSO
- Roles
- Permissions
- Invites
- Password reset
- Audit log
Each person who signs in sees what their role allows, and the audit log records who changed what.
Data
- Multi-tenancy
- Backups
- Migrations
- Encryption
- Data residency
- Retention
- Exports
- Redaction
Every customer’s data stays apart from every other customer’s, and last night’s backup actually restores.
Money
- Billing
- Subscriptions
- Invoices
- Tax
- Refunds
- Usage metering
- Webhooks
- Failed payments
Billing that survives a failed card and a refund.
Reliability
- Monitoring
- Alerting
- Logging
- Rate limits
- Retries
- Rollback
- Load testing
- Uptime
When something breaks at 2 a.m., you hear about it before a customer does, and the last good version is one step back.
AI safety
- Evals
- Guardrails
- Fallbacks
- Prompt versions
- Cost limits
- Human review
- Grounding
- Drift alerts
The model’s answers are tested before each release, and someone gets told when they start to drift.
Not every product needs all 48 on day one. SSO, data residency or right-to-left may not apply to you yet. The blueprint lists which ones ship, and in which week.
What the audit decides
Your prototype isn’t thrown away. The audit goes through it part by part and puts each piece in one of three columns.
Keep
What already works for your users stays.
- The screens and flows your users already know
- Business logic that’s already right
- The data you’ve collected, migrated rather than re-entered
- Your stack, where it holds up under review
Rebuild
What can’t carry real users gets rebuilt.
- Logins added as an afterthought
- A data model with no line between one customer and the next
- Keys and secrets that sit in the browser
- Payments wired to a test account
- Database changes made by hand, with no migrations
Add
What a prototype never needed gets added.
- Monitoring and alerting
- Backups, restored once to prove they work
- Evals and guardrails for the AI parts
- Rate limits, retries and rollback
- An admin panel for your team
You get the three columns in writing at the end of the audit week, with the reasoning for each call. They’re yours whether or not you build with us.
How it runs
One week of audit, one week of blueprint, then the build. You watch the timeline instead of being told about it.
- 1 week
Audit
We read the code that exists and the data and workflows around it, then rank what’s worth building. If nothing on the list is worth it, we say so, and you keep the process map, the ranking and the reasoning.
- 1 week
Blueprint
We write down how the system will be built, what’s in scope and what ships in which week, then put a fixed price on the build. The blueprint is yours to keep, whether or not you build with us.
- 4–8 weeks
Build
A working build, demoed to you every week, running on something you can click. Production pieces land on top of what the audit said to keep.
- Ongoing
Run
Two ways to go. We run it, with hosting, monitoring and support on a monthly retainer. Or we hand it over completely: the code, the documentation, the eval setup and access to everything. It’s a choice, not a dependency we engineer in.
Two weeks in, you know what stays, what gets rebuilt and what the build costs, in writing. You can walk away with all of it.
- A working build every week
- You own the code
- We run it, or hand it over
A typical build
This is the shape of a four-week build for a focused prototype. Bigger ones take longer, up to eight weeks. Your blueprint sets the real plan, with what ships in which week, in writing, before the build starts.
- AuditBefore code
Read and sort
We read the code, the data and how it runs, and sort every part into keep, rebuild or add.
- BlueprintBefore code
Plan and price
Scope, a week-by-week plan and the fixed build price, in writing.
- Week 1Demo
Foundations
Logins, roles and the line between one customer’s data and the next. Staging and production environments, and deploys you can roll back.
- Week 2Demo
Your product, and money
The features your users rely on move across, and your existing data is migrated and checked against the original. Billing goes in, including what happens when a card fails or a customer asks for a refund.
- Week 3Demo
Reliability and AI safety
Monitoring, alerting and logging, and backups restored once to prove they work. Evals and guardrails for the AI parts, cost limits, and a load test at more users than you expect.
- Week 4Demo
Launch
Your pilot users move over, and we watch the first real traffic together. Then you choose: we run it, or we hand it over.
FAQ
If your question isn’t here, ask it when you write. We reply within one business day.
We built our prototype with AI coding tools. Do we have to start over?
No. It’s a common starting point, whether the prototype came from AI coding tools, a freelancer or another team. The audit tells you what to keep, what to rebuild and what it costs. What a prototype usually lacks is the layer underneath: logins and roles, each customer’s data kept apart, billing and monitoring.
How long does it take to take a prototype to production?
One week of audit and one week of blueprint, then 4–8 weeks of build. You see a working build every week, so you’re watching the timeline rather than being told about it. If your date is closer than that, tell us when you write and we’ll say in our first reply what’s realistic.
How is the price set?
We price the audit as a fixed fee before you commit. If it shows the build isn’t worth doing, you stop there and keep the findings. Otherwise a one-week blueprint follows, and at the end of it, two weeks in, the build price is fixed in writing before we write code.
What happens to our existing users and data?
They come with you. The audit maps where your data lives today, the blueprint plans the move, and your data is migrated and checked against the original before anyone switches over. Your users move once, when the new version is ready for them.
Will you keep our current stack?
Where it holds up, yes. The audit looks at the code, the hosting and the services it depends on, and recommends a change only where the current choice won’t carry real users or would cost you more to keep. Every recommendation comes with its reasoning.
What if the audit finds security problems?
They go to the top of the list. Anything that exposes customer data or keys is written up in the audit week with what it takes to fix, and the blueprint schedules it before anything else.
Will AI write my code? Who actually does the work?
Senior engineers, led by the person who designs your system. They make the architecture decisions, and they’re the people you talk to. AI agents work alongside them on implementation and testing, which is how a senior team ships in weeks. You deal directly with the people building it, from the first call to handover.
Who owns the code, and what happens if we stop working together?
You do, unless you choose another licensing model, and whichever you choose is agreed in writing before work starts. You see a working build every week, so stopping never means starting from nothing. If we part ways, the handover includes the code, documentation, the eval setup and access to everything we set up.
Is this right for an early-stage idea?
Build engagements fit best when there’s a real product or workflow with users behind it. If you’re still finding out whether anyone wants it, keep building with the AI tools. They’re good at exactly that stage. Talk to us when someone is about to depend on it: a pilot customer, a second account, a first invoice.
A few lines is enough. We reply within one business day.
Or write directly:hello@dynode.ai+1 332-456-0669