The Forge: the production system behind every engagement

Every Entatan project, partner or venture, runs on the same production system. We call it The Forge. It is not a product you can buy. It is the reason a small team can carry a sprint, a creative calendar, and an ad account at the same time, and it is worth explaining because partners ask what they are actually paying for.

What it is

The Forge is four things that most agencies keep separate or do not have at all.

• Agents. A roster for code generation, review, QA, copy, creative variants, reporting, and research, each with a written boundary and an evaluation set.
• Tooling. One environment per project with the repo, the design system, the ad accounts, the analytics, and the agent roster wired together on day one.
• Compute. Reserved model capacity and build infrastructure so a sprint never waits on a queue.
• Cadence. Two-week sprints, a daily async update, a weekly growth review, and a demo on day ten. Every project, no exceptions.

Why build it once

The alternative is rebuilding it per engagement, which is what most services work looks like from the inside: a new repo, a new folder of brand assets, a new reporting spreadsheet, and three weeks of setup billed as discovery. We did that once and refused to do it again.

Building the system once means the first pull request on a new engagement ships on day one. It means every agent improvement lands on every project. And it means the lessons from a venture that had to find its own customers show up in the next partner sprint.

A day inside The Forge

Here is what a typical weekday looks like across projects.

1. 06:00. Overnight agents finish: test suites, dependency updates, ad performance pulls, and a draft of each project's daily update.
2. 09:00. Engineers and creatives review the drafts, correct the ones that are wrong, and post the updates to partner channels.
3. 10:00. Build. Most of the day is design decisions, integration work, and the parts of the problem that need a person.
4. 15:00. Review. Every pull request gets an agent review and a human review. Every ad variant gets a performance check and a brand check.
5. 17:00. Handover. Agents write up what changed, update the demo environments, and queue the next night's runs.

By the numbers

We keep a public page for The Forge with these numbers and update it as the system grows.

What it is not

The Forge is not a promise that agents do everything. Roughly, agents do the mechanical work and people do the judgment work, and the line moves a little every month. It is also not lock-in. Everything we build for a partner lives in the partner's accounts and repos, and the handover doc that closes each sprint is written so another team could pick it up.

We built the system we wished every agency we ever worked with had. Then we made it the only way we work.

More on The Forge, including the full agent roster, is on its page.