How we take an early product to production, from scoping call to handover

By Alvi Lika, Founder, Soatech

· · 5 min read

How a Soatech engagement runs for an MVP or AI-built prototype: the scoping call, the written scope, weekly increments, senior review and handover, plus which engagement fits which starting point.

This is how Soatech works on an early product: an MVP that needs to reach paying users, an AI-built prototype that needs production foundations, or an existing SaaS adding an AI feature. It covers the same steps as How we work, in more detail, with what you receive at each stage and what we ask of you.

An earlier version of this article described a day-by-day "MVP Sprint" and a set of engagements that are no longer offered, along with speed and test-count claims that weren't backed by records. Those have been removed. The current engagements are below.

Which engagement fits your starting point

Your situationEngagementPrice and length
You have a prototype or codebase and need to know what is unsafe or missing before deciding anythingProduction Audit€1,500 fixed, 3–5 working days. A written report and a 45-minute walkthrough. No code changes
An AI-built prototype (Lovable, Bolt, v0, Cursor) needs the standard production baselinePrototype to Production€3,500 fixed, about one week, against a written baseline scope
One defined feature needs to ship to production, without an ongoing commitmentProduction Sprint€5,000 fixed, about two weeks, one agreed feature
A funded SaaS team needs AI features designed, built and shipped over monthsEmbedded Architect€7,500 per month, month to month

If you continue after a Production Audit, its fee is credited in full toward a Production Sprint or the first Embedded Architect month. Prototype to Production covers a written baseline. A larger gap is scoped separately rather than absorbed. Full details are on the engagements page.

These engagements assume there is something to work on: a prototype, a codebase or a product. If you're starting with no code, say so on the scoping call. We'll tell you whether any of them fits, or that it doesn't.

Step 1: scoping call (30 minutes)

You speak with a senior architect, not a salesperson. The call covers what you are trying to ship, the constraints (stack, deadline, data, who uses it) and what "done" means to you. If it isn't a fit, we say so on the call.

To make the call useful, bring repository access or a demo, the feature or gap in a sentence or two, and the date that matters.

Step 2: written scope, fixed price

Before any work starts you receive a written scope containing:

  • the outcome and the acceptance criteria it will be checked against;
  • what is not included, stated explicitly;
  • what we need from you (access, a decision maker, someone to accept the work);
  • the architect who will do the work and the senior reviewer, both named before work starts.

The price is fixed against that scope. If the work turns out to need more than was agreed, we tell you and re-scope in writing. Nothing is absorbed silently and nothing is billed by surprise. For what a good scope document looks like, see how to scope a software project.

Step 3: weekly shipped increments

Work happens in your repository, following your branching and review conventions. Each week, working changes land in your codebase with a short written update: what shipped, what is next, and which decisions we need from you.

For a prototype, the early increments usually go to the foundations the demo skipped, in roughly this order:

  1. Data isolation. Every tenant-owned record is scoped, and a test signs in as two tenants to prove neither can see the other's data.
  2. Auth and sessions. Session configuration, what the client can read, and password and magic-link flows.
  3. Payments. Webhook signature verification and idempotent handling of repeated events.
  4. Failure handling. Explicit retry and timeout policy for third-party calls, especially model APIs.
  5. Tests on the paths that carry money and data. End-to-end coverage where a regression would be expensive.

The order changes with the codebase. The Production Audit exists to find which of these matter most in yours.

Step 4: senior review on every release

Everything that merges is reviewed by a senior architect, named in the scope. There are no junior engineers in the delivery chain. Review is aimed at the problems tests miss: a query that skips the tenant filter, a session callback that returns too much, a retry loop with no deadline.

Step 5: handover

You finish with the code in your repository, documentation of what was built and why, and the decisions that are still open. Custom deliverables are assigned to you on payment of the related fees (Terms of Service, section 5). An Embedded Architect engagement ends on written notice from either side, with the period set in the signed agreement, and the final month includes handover documentation so your team can carry on.

What these engagements do not include

  • Penetration testing, compliance certification or legal compliance opinions. We can prepare a codebase for those reviews, but we don't perform them.
  • Unlimited output or an open request queue. Capacity is agreed in writing.
  • Executive or hiring responsibilities. An Embedded Architect owns the architecture and delivery of agreed work, not technical leadership of the company.
  • On-call support around the clock, unless separately agreed.

Where the engineering patterns come from

The production patterns above (tenant scoping, schema-validated model output, a human review gate, sealed signatures, idempotent payments) are the ones running in wintura.ai, the studio's own product. The Wintura decision record explains each one and what it costs. Soatech is founder-led and based in Tirana, Albania, working on Central European Time. Each engagement is delivered by a senior architect from a small network, matched to the problem.

Not sure which engagement fits? Start with a 30-minute call.

Discuss your project

Working on a feature this article touches? A 30-minute call is the quickest way to scope it.

Discuss your project