From Prototype To Production

What is included

• Start with an Architecture Assessment: one repository, one application, one primary data store and up to three priority user journeys, within eight engineering hours. We confirm repository size and stack suitability before accepting the work.
• Review module boundaries, dependencies and error handling; identify appropriate design patterns and where simpler code is sufficient. Assess domain models, data structures, database relationships, constraints, indexes and migration needs against your actual use cases.
• Review authentication and authorisation boundaries, input validation, secrets handling, dependency risks and automated test coverage. This is an engineering review; a dedicated security assessment is separately scoped.
• The Refactoring Sprint implements one agreed priority workstream in the same application, covering up to three existing user journeys within 32 engineering hours. A validated assessment and written acceptance criteria are required first; the assessment fee is separate.
• Within that sprint, refactor the agreed modules and data model, add regression tests and relevant failure-case tests, and document the resulting design. Changes to data include a migration and recovery approach tested with representative non-production data.
• Configure repeatable local setup and an automated build/test pipeline for the agreed stack. Validate the scoped changes in staging, document release and rollback steps, and provide a 60-minute technical handover.

What you receive

• Assessment: current-state architecture and data-model diagrams, prioritised engineering findings, a proposed target design and a phased implementation backlog with acceptance criteria.
• Refactoring Sprint: reviewed source changes in your repository, applicable schema migrations, automated tests and a build/test pipeline for the agreed workstream.
• Refactoring Sprint: README and local setup instructions, configuration reference with no secrets, architecture decision records, updated data-model diagrams and interface/API documentation for changed components.
• Refactoring Sprint: deployment and rollback runbook, operating and troubleshooting notes, known limitations and a handover recording or written handover notes by agreement.

How we check it works

For the assessment, walk through the findings, diagrams and prioritised backlog with you. For a sprint, the agreed user journeys pass on a clean setup and staging environment, the automated build and agreed tests pass, and a developer can follow the setup and handover documentation. Where data changes are included, test the migration and agreed recovery procedure. Remaining risks and unfinished work are recorded; production release is a separate go/no-go decision.

Running costs and optional care

Assessment starts at US$990 once-off; a Refactoring Sprint starts at US$4,490 once-off. Assessment plus one sprint starts at US$5,480. Prices exclude VAT, hosting, build runners, external APIs and licences. There is no mandatory support retainer. Additional work and ongoing application support are separately scoped and approved before it starts.

Scope boundaries

No promise to rebuild or make an entire application production-ready for the starter price. New features, complete UI redesigns, replacement of the full architecture, additional repositories, large or live production-data migrations, formal penetration testing, compliance certification, 24/7 operations and unlimited revisions are excluded. Production deployment, load testing and additional integrations require explicit scope and pricing. Design patterns are selected to solve documented problems, rather than added for their own sake.

Before we start

You own or have permission to modify the source and supply repository access through an agreed secure method, setup instructions, the current stack, sample data without customer secrets, a technical contact and your priority user journeys. We check stack compatibility and whether refactoring or rebuilding is the sensible route. A sprint needs our assessment or an equivalent assessment we can validate; discovery is not bundled into its 32 implementation hours.

Delivery and handover

A free 30-minute scoping call establishes fit. Assessment and sprint dates are agreed after repository review. We agree the backlog, acceptance criteria, hour limit and review milestones before each engagement. Work pauses at the approved limit; new requirements or additional hours require a separate approved quote. The sprint includes one review of its agreed acceptance criteria and the technical handover within its hour limit.