Ticket in. Review-ready merge request out. Built around your tickets, your repo, and your reviewers.
The problem
AI writes the code. Shipping it is still hand-cranked.
A ticket does not become a merge request by itself.
Someone reads the ticket and writes a plan.
Opens a branch, implements the change with tests.
Opens the MR, answers every review comment, chases CI green.
Frontier models can write the code. The execution loop around the code
— the project-management busywork of delivery — is still manual, and it is most of the elapsed time.
Why now
The models got good enough — the wrapper didn't exist.
Frontier coding models can now run an entire ticket → MR loop unsupervised
— up to the review gate — but only when they're wrapped in the team's real context
instead of a blank editor:
The ticket
What to build, in the team's own tracker.
The repo
Real code, real branches, real CI.
The conventions
The rules the team already wrote down.
The review pipeline
Where a human still decides.
The missing piece was never a better autocomplete. It's the orchestration layer.
The solution
Forge: a ticket becomes a review-ready MR.
reads the ticket→writes a plan→opens a branch→implements + tests→opens a Draft MR→replies to review→reacts to CI
Forge delivers. Humans approve.
Plan, code, review-ready MR — start to finish. The merge stays a human decision.
Reads your CLAUDE.md / AGENTS.md / CONTRIBUTING.md. Follows your rules; doesn't reinvent them.
Auditable
Every commit carries a Co-Authored-By trailer. Plans, specs & research persist in the repo.
Human-gated
MRs open as Draft. Merge to the default branch is the hard human gate.
Where Forge sits
One layer up, one layer closer.
Coding tools complete a line. AI agents augment a developer. Forge replaces the project-management busywork of delivery.
One layer higher than the coding assistants; one layer closer to your team than the
autonomous agents — built around your tickets, your repo, and your reviewers.
Embedded in the real repo + review pipeline, not a sandbox.
Convention-driven — follows the rules you already wrote.
Auditable by construction — a paper trail, not a black box.
No lock-in — cancel any time, keep everything.
Model-agnostic harness: Forge is the orchestration layer, so it compounds as frontier models improve.
Proof
Forge builds Forge.
Forge is developed by Forge. New features land as tickets that Forge itself
plans, implements, and opens MRs for — reviewed and merged by the team.
A durable decision log lives in the repo: plans/, specs/, research/.
Ticket IDs in every branch and MR title; every commit signed.
This deck was produced by a Forge session.
Dogfooded on its own repo — in the open, every commit reviewable.
Market
Why this is big.
Founder input needed
Proposed logic to fill in with real numbers:
Wedge: ticket-driven teams & software agencies with an existing tracker + review pipeline.
TAM / SAM / SOM: AI-assisted dev-tooling spend → delivery-automation slice → beachhead segment.
Expansion: from single tickets to whole backlogs; from one team's conventions to any team's.
Sizing to be provided / confirmed by the founders.
Business model
How Forge makes money.
Needs Delivery + CPO sign-off
Proposed shape (commercial terms must be confirmed before this goes to investors):
Before you sign, we read the backlog with you, sequence it, and give you a roadmap with a price attached to each stage.
Human-led pilot scoping — not an automated estimate.
No lock-in — cancel any time, keep everything.
Pilot length, pricing model, and fixed-price terms to be confirmed by Delivery lead + CPO.
Traction
What's real today.
Founder input needed
No numbers invented for an investor deck. To fill in:
Tickets planned & MRs opened by Forge to date.
Self-hosting milestone(s) — features Forge shipped for itself.
External pilots / design partners / revenue, if any.
Metrics to be provided by the founders.
Team
Who's building this.
Founder input needed
A technical infra fund weighs the team heavily. To fill in:
Founding team, roles, and one-line credibility per person.
Relevant infra / dev-tools / delivery track record.
Advisors, if any.
Bios to be provided by the founders.
Vision
From a ticket to a backlog.
Today Forge carries one ticket to a review-ready MR. Next: take a whole backlog —
sequence it, price it, deliver it — with a human review gate on every step.
The execution layer for any ticket-driven team.
The ask
What we're raising.
Founder input needed
To fill in:
Amount & stage: how much, at what round.
Use of funds: what the capital buys (team, GTM, infra).