Discovery call
~1 weekWe learn how your organization actually works today — the systems, the constraints, the people who have to sign off. No SOW gets written before this happens.
BUILT FOR ORGANIZATIONS WHERE SOFTWARE FAILURE HAS REAL CONSEQUENCES
Healthcare
Financial Services
Manufacturing
Government & Public Sector
Regulated Enterprise
§00 — WHAT'S INCLUDED
Everything it takes to ship and run production software.
One engagement, one accountable team. Nothing you have to separately staff, integrate, or chase.
- Delivery team
- Dedicated pod with named owners, not a rotating bench
- Scope
- Full lifecycle — discovery through operate, on the same governed pipeline as Stack18 Platform
- Infrastructure
- Hosted and operated by Stack18, or deployed into your own cloud environment
- Security review
- Architecture and access review before any code reaches production
- Reporting
- Weekly syncs, a shared roadmap, and a live audit trail you can open any time
- Support
- SLA-backed response times, defined in your statement of work
- Ownership
- Full source code, IP, and documentation, transferred on completion
§01 — HOW AN ENGAGEMENT RUNS
From first call to a system you own.
The same four-layer pipeline that powers Stack18 Platform, wrapped in a managed engagement with named humans accountable for every step.
Scoping & statement of work
1–2 weeksA written scope, timeline, and price — reviewed against your procurement and security requirements before anyone signs.
Kickoff & discovery layer
2–3 weeksYour delivery pod is named. Business discovery and requirements gathering produce a signed PRD before design work starts.
Design & build sprints
Scoped to the buildArchitecture, UI/UX, and code generation run in sprints with weekly syncs and a live roadmap. Every layer ends with your sign-off before the next one loads.
Launch & handover
1–2 weeksProduction deployment, documentation, and a full IP and knowledge transfer to your team — or straight into ongoing Stack18 support.
Ongoing support
Optional, ongoingMonitoring, maintenance, and a continuous improvement roadmap under an SLA — or we step back once your team is ready to run it alone.
§02 — YOUR DELIVERY POD
Named people, backed by the full agent roster.
Every engagement is led by people you can call, not a ticket queue. They direct the same nine specialized agents that power Stack18 Platform.
Lead
Engagement Lead
Your single point of accountability — owns the roadmap, the relationship, and every commitment.
Architecture
Solutions Architect
Designs the system against your constraints, your compliance needs, and your existing stack.
Delivery
Delivery Manager
Runs the sprint cadence, the weekly sync, and keeps the roadmap honest.
Assurance
QA & Security Lead
Owns the review gates — code quality, security posture, and compliance sign-off.
§03 — SECURITY & GOVERNANCE
Built to survive an audit, not just a demo.
Enterprise engagements run under the same governance model as Stack18 Platform, with additional review built in for regulated environments.
Architecture review
Every system design is reviewed against your security and compliance requirements before build starts.
Access control
Role-based access to code, infrastructure, and data, scoped to what each person and agent actually needs.
Full audit trail
Every decision, from requirement to deployment, is logged and traceable — reviewable at any time, not just at handover.
Data handling
Your data stays in the environment you specify. Nothing leaves your infrastructure without a documented reason.
Incident response
A defined escalation path and response times, agreed in your SOW before the engagement starts.
Offboarding
A documented exit plan from day one — code, infrastructure, and knowledge transfer, whenever the engagement ends.
§04 — ENGAGEMENT MODELS
Three ways to bring Stack18 in.
Every model runs on the same governed pipeline and the same delivery pod structure — the shape changes to fit what you're solving for.
Full Build
Custom product
A net-new platform, designed and built end to end against your business logic and compliance requirements, then handed off or kept under ongoing support.
For: enterprises & scale-ups shipping something new
Rebuild
Legacy modernization
We read, document, and rebuild systems nobody fully understands anymore — re-architected and re-platformed without stopping the business that depends on them.
For: organizations with critical legacy estates
Embedded Stack
Ongoing capacity
A standing delivery pod and agent roster embedded alongside your team, extending an already-full roadmap for as long as you need it.
For: teams that need permanent extra capacity
§05 — WHAT YOU OWN
Nothing you build with us stays with us.
- Source code
- Full repository access from day one, full ownership on completion
- Documentation
- PRDs, architecture diagrams, and runbooks — yours to keep and extend
- Infrastructure
- Deployed in your cloud account, or transferable on handover
- Vendor lock-in
- None by design — standard languages and frameworks, no proprietary runtime
- Exit
- A documented offboarding plan, agreed before the engagement starts
§06 — QUESTIONS, ANSWERED
FAQ
How long does a typical engagement run?
It depends on scope. A focused rebuild might run a few months; a full platform build or an embedded, ongoing pod can run for years. Timelines are set during scoping, before anyone signs a statement of work.
Can you work inside our existing cloud environment?
Yes. We can deploy into your AWS, Azure, or GCP account under your existing controls, or host it ourselves if you'd rather not run the infrastructure. Either way, it's specified in the SOW.
How does pricing work?
Enterprise engagements are scoped and priced individually based on the size of the team, the length of the engagement, and how much of the stack you want us to run versus hand over. We'll walk through this on the discovery call.
What happens to our data?
Your data stays inside the environment you specify. We don't move it anywhere without a documented reason and your sign-off, and access is scoped to exactly what the engagement requires.
Do we need our own engineering team for this?
No — the delivery pod covers the full lifecycle. If you do have an internal team, we can work alongside them, hand off cleanly at any layer, or run entirely independently. It's your call.
What happens after launch?
You can take full ownership and run it with your own team, or keep Stack18 on under an SLA for monitoring, maintenance, and continuous improvement. Both paths are planned for from day one.
READY TO SCOPE AN ENGAGEMENT?
Tell us what you're building.
Book a discovery call — no statement of work, no commitment, just a conversation about what you're trying to build and whether Stack18 Enterprise is the right fit.