Four ways to put a team on it.
Figures below are starting points for a single deployment. Final scope moves the number, and we confirm it in writing after the briefing rather than after the first invoice.
Architecture roadmap
Interviews, a read of the systems, and a written roadmap: what to build, in what order, with estimates and the things we would not attempt. Credited against a build if you go ahead with us.
Fixed-scope deployment
One system, specified up front and delivered into production inside your cloud, with handover included rather than sold separately. Payment is staged against releases, so you are never far ahead of what exists.
Embedded co-development
Engineers inside your team on a standing schedule, building and teaching at the same time. Right when scope will keep changing and you want the capability to stay in the building.
Run and improve
Monitoring, model and cost review, small improvements, and someone to call when something breaks — that someone answers at support@alotlabs.com. Only offered on systems we built or have read end to end.
For scale: $18,000 buys a two-week roadmap, against the nine-month discovery engagement it replaces.
Model and infrastructure costs are yours and run on your accounts, inside your VPC, so you can see them and take them with you.
We do not mark up licenses or resell anyone's platform, which means the recommendation is not quietly a commission.
Anything we build for you stays yours. Our deployments come in as a starting point, not as a license you have to keep paying for.
These are our figures. The useful question is what the other three routes cost over the same weeks — a large consultancy, two senior hires, or a contract build team. The calculator on the compare page runs all four side by side, on rates you can change to yours.
Run the comparisonIt does not. We deploy inside your VPC on Bedrock or Vertex AI, with zero-data-retention configurations and PII masking in the middleware. Nothing routes through infrastructure we own.
The people in the briefing write the code, and the first deliverable is software rather than an assessment. We also arrive with working infrastructure instead of billing you to build it from scratch.
Model calls sit behind an interface, so swapping a provider is a configuration change and a re-run of the evaluation set, not a rebuild. On a run-and-improve retainer we handle the swap before you notice.
That is the test we hold ourselves to. Handover includes the source, the architecture documentation, the runbook and working sessions with the team who will own it. If they cannot change it themselves, the engagement is not finished.
You do, from the first commit, in your repository. Our deployments come in under a license that survives the engagement at no ongoing cost, and anything built on top of them is yours outright.
A roadmap can usually start within two weeks of the briefing, and a build within four. Security review is normally the long pole, so we start that paperwork in parallel rather than after signature.