Modernise old systems and harden prototypes — without the big-bang cutover.

What gets reviewed. The codebase (or the no-code app). The data structure. The integrations. The infrastructure. The dependencies. The security posture. The bus factor (how many people understand it).

What you receive. A risk register ranked by likelihood and impact. A data inventory with quality assessment. A modernisation roadmap with staged rebuild plan. A fixed-price quote for the next stage. A clear "do nothing" baseline so you can weigh the modernisation case against actual risk.

What this is NOT. A sales pitch dressed as a report. We will tell you honestly if the legacy system has another five years in it, or if the prototype is well-built enough to scale as-is. The audit is the same price either way.

Where data lives. Access databases, SQL Server / MySQL / Postgres, Excel and CSV, FoxPro / dBase, proprietary file formats, custom internal systems, vendor SaaS exports.

How it moves. Schema mapping to the new structure, with cleanup and validation at the door. Reference data (customers, products, accounts) deduplicated before it lands. Historical transactions preserved with relationships intact — not flattened into opening balances.

What the team gets. Full data history in the new system. Audit trail of every record migrated. Reconciliation report showing source counts, destination counts and exceptions. The new system starts on Day 1 with the full story, not a fresh slate.

What we build with. React, Node, Postgres, AWS — proven, well-supported, well-staffed. Mobile where mobile makes sense. Web portals where web makes sense. Native integration with the platforms your business already uses (Xero, MYOB, ServiceM8, etc.).

What we preserve. The workflow your team already knows. The reports the business depends on. The forms and screens people use every day — improved where they obviously needed improvement, kept where they were already fit for purpose. Not a redesign for redesign's sake.

How it goes live. Stage-by-stage. The most critical piece of the workflow first, in parallel with the old system. Each stage proven before the next begins. Cutover is a planned moment, not a leap of faith.

Common starting points. Bubble apps that hit performance ceilings. Replit-deployed prototypes that need to scale beyond hobby plans. Cursor / Claude Code / v0 / Lovable apps that look polished but have security and reliability gaps. Webflow + Make.com stacks that need to handle real transactions.

What we typically do. Audit the AI-generated or no-code code. Identify what to keep, what to rewrite, what to throw away. Move data to a proper database. Rebuild the backend on a production stack. Keep the UX your customers already know — same product, better foundations.

The honest part. Sometimes the prototype is good enough as-is. Sometimes it needs a partial rebuild. Sometimes the cleanest path is a fresh build using the prototype as the spec. The audit tells us which — and you get the truthful answer.

Where it runs. AWS in your own account or ours. Backups, monitoring, alerting and security patching all configured properly. SSL, authentication, audit logging. Cost-controlled — we right-size the infrastructure, not over-provision.

Documentation. Architecture diagram, deployment guide, runbook for common issues, contact list. Written so a new developer can pick it up — your business is not held hostage to one person's knowledge.

Ongoing support. Optional monthly support agreement covers bug fixes, dependency updates, security patches, small feature additions and on-call response. The same team that built it stays available — but the documentation means you can take it elsewhere if circumstances change.

For: any business with a legacy system, prototype or custom app where the next step is unclear. Particularly useful when there is internal disagreement about whether to rebuild, replace or extend.

What you get: Codebase / no-code app / database audit. Data inventory with quality assessment. Risk register ranked by likelihood and impact. Modernisation roadmap with staged rebuild plan. Fixed-price quote for the recommended next stage. Honest "do nothing" baseline.

Timeline: 2 to 4 weeks depending on system size and access. Fixed-price after a 15-minute scoping call. You walk away with a clear path even if you choose not to engage us for the rebuild.

For: situations where part of the legacy system needs to be modern (often the customer-facing or compliance-critical part) and the rest can keep running for now. The most common engagement.

What you get: Data extraction from the legacy system. Modern web (or mobile) rebuild of the critical workflow. API layer connecting the new system to the old where they need to coexist. Hosting setup, monitoring, documentation. The old system keeps running in parallel through the transition.

Timeline: 8 to 16 weeks delivered in stages. First critical workflow live inside the first month. Old system retired stage by stage as the rebuild covers more ground. Fixed-price.

For: compliance-driven full modernisation. Or for prototypes (Bubble / Replit / Cursor / AI-built MVPs) that need a complete rebuild on production foundations. Or when the legacy system has reached end-of-life and incremental rescue is not enough.

What you get: Complete modern platform — web + mobile + API + database + hosting + monitoring + documentation + ongoing support. UX preserved or improved where appropriate. Data and history migrated cleanly. Old system retired at the end of the engagement.

Timeline: 3 to 9 months in clearly defined stages. Each stage delivers measurable value before the next begins. Fixed-price per stage. Ongoing support agreement once live.