Founding program
We build your AI-native SDLC. You keep everything.
12–16 weeks embedded with your engineering team. Orchestration, governance, and workflow automation built on your infrastructure. Open source. Yours to own and extend.
Weeks embedded
Team at a time
Open source
Exit if thesis fails
Principles
How we work.
Not consulting. Not managed services. A focused build with structural safeguards against scope drift.
Your infrastructure
Your cloud. Your VPC. Your security controls. We never host your data or code.
Open source
Everything we build is OSS. Fork, extend, contribute back, or diverge. No lock-in.
Your team owns it
At week 16, your team operates independently. No ongoing dependency unless you want it.
Thesis-driven
Clear hypothesis going in. If it's wrong, we stop and refund. No burning 16 weeks on the wrong problem.
The engagement
16 weeks. Four phases. One running system.
If the hypothesis doesn't validate in phase one, we stop. You don't pay for work that won't deliver value.
Hypothesis validation
Map your engineering workflows. Observe how AI tools are used. Validate whether coordination and governance are the actual bottlenecks. If they're not, we stop and refund.
SDLC workflow mapping
AI tool usage audit
Bottleneck validation
Go/no-go decision
Core infrastructure build
Build the foundational orchestration and policy infrastructure. Deploy in your environment. Integrate with GitHub, CI pipelines, and team workflows.
Orchestration engine on your cloud
Policy engine configured
PR classification and routing
Workflow automation live
Deploy and iterate
System runs on real engineering work. Iterate based on what your team actually needs. Fix what breaks. Extend coverage.
Handling live PRs
Team using it daily
Observability dashboard
Full audit trail
Stabilize and hand off
Harden the system. Document everything. Transfer full operational ownership. Your engineers extend and maintain it independently.
Production-hardened
Documentation complete
Team trained
ADRs for every choice
Deliverables
What your team has at week 16.
Not recommendations. Not a slide deck. Running infrastructure your team uses every day.
AI workflow orchestration
Configurable workflows routing AI-generated changes through risk-appropriate review paths.
Policy enforcement
Declarative policies: what auto-merges, what needs review, what needs senior sign-off.
Org-wide visibility
Dashboard showing what AI agents are doing across your engineering org. No invisible risk.
Audit trail
Every AI action logged, attributed, queryable. Compliance-ready from day one.
Team autonomy
Engineers trained on extension and maintenance. Full documentation, runbooks, ADRs.
Fit
Is this right for your team?
Good fit
Not a fit
One engagement at a time. Full attention.
This is founder-led work. If the timing doesn't work now, we'll let you know when the next slot opens.
Book a conversationFAQ
Common questions.
Something not covered? Book a conversation.
What do we get at the end of 16 weeks?
A running, open-source orchestration and policy system in your environment. It classifies AI-generated changes by risk, routes them to the right reviewer, enforces your policies, and gives you a full audit trail.
What if the problem isn't what you expected?
We validate in weeks 1–2. If your bottleneck differs from our hypothesis, we pivot the engagement or stop early with a partial refund.
Is this consulting?
Consulting delivers recommendations. We deliver a running system. At week 16, you have infrastructure your team uses every day.
Why open source?
You own it with zero lock-in. And it forces us to build generalizable infrastructure rather than bespoke scripts. Every component must be useful to the next team too.
What's the relationship to LoomStack?
This program is how LoomStack gets built. Each engagement contributes to the open-source core. You get the team building the category-defining product, applied to your environment.
What happens after the engagement?
You run it independently. If you want ongoing support and priority access to new capabilities, we offer that separately.
How does this differ from the Design Partner Program?
Design partners co-create over time. This program delivers a working system in 16 weeks. Different timeline, commitment, and outcome.