Build Your AI Team Before You Deploy It

Most self-hosted software greets you the same way: a fresh install, an empty screen, and a long "now what?" Powerful, yes — but you're doing the assembly. For an AI office, that means five agents booting up with no idea who you are, what your business does, or which model each of them should run.

There's a better order of operations. Design your team first, then deploy it. Walk in with the roster already decided, the models already assigned, and your company already described — so the box that installs on your server arrives set up for *your* business, not a generic one. That's exactly what the free AI Team Builder is for.

The blank-slate tax nobody mentions

When an AI team starts with zero context, the first hours are spent teaching it the basics: what you sell, how you talk to customers, which agent handles what, and — the part that quietly burns money — which model each role should use. Guess too high and every routine email runs on a frontier model you're overpaying for. Guess too low and your coder stumbles on real work.

None of that is hard. It's just friction, and friction at the exact moment you want to see the thing *work*. Doing it up front, before anything is installed, turns a fiddly first day into a two-minute form you fill out while you're still deciding to buy.

What you actually decide in two minutes

The builder asks about your business — your industry, your size, whether you write code or produce visuals, how sensitive your data is — and turns your answers into a concrete roster you can adjust:

• The right roles for you. A local service business leans on a secretary; a software shop wants a strong coder; an online store needs a copywriter for product and marketing. You get a starting team that fits, not a fixed five.
• A model per role, priced live. Each agent is matched to a model that suits its job, with prices pulled straight from the live catalog — a strong model where it earns its keep, a cheap capable one everywhere else. (More on that logic in picking a model for each role.)
• Your real monthly cost, before you pay a cent. A live estimate updates as you tune roles and volume, so you know the running cost of your office up front — no surprises after install.
• Your company, in their heads from minute one. The description you give becomes the context every agent carries, so they answer as *your* office, not a blank assistant.

Nothing is locked. Swap a role, change a model, edit the company blurb — the numbers move in real time. When it looks right, you save it, and the plan is yours to keep whether or not you buy today.

Why "before you deploy" is the whole point

Here's the part that makes it more than a calculator. Your saved plan is a blueprint, tied to your email. When you install OfficeForge with that same email, the box finds the blueprint and applies it automatically — the roster, the per-role models, and your company description are written straight into the agents as they come up. You add your own model key, and the office is live and already yours.

Compare the two first days:

• Without a blueprint: install → blank office → walk the coder through your business, roles and models in chat → then start working. It works, and the coder is good at it — but it's a setup session before the payoff.
• With a blueprint: install → the office comes up already staffed and briefed for your business → add your key → start working. The setup happened before you deployed, while it cost you nothing.

Same destination, minus the blank-slate step — and you arrive already knowing what the office will cost to run.

One funnel, no busywork

Because the plan travels with your email, there's no copying settings, no config files, no "export/import." Build the team, buy with the same address, install — the box does the wiring. It's the difference between assembling furniture from a box of parts and having it arrive built.

And if you'd rather not plan ahead? Skip it. Install a standard office and set everything up afterward in a guided chat with the coder agent — same result, just configured after the fact instead of before. The point isn't that you *must* build first; it's that building first is faster, cheaper to decide on, and lets you see the price tag before you commit.

Try it, then deploy it

Spend two minutes in the AI Team Builder: answer a few questions, watch your team and its monthly cost take shape, and save the plan. If OfficeForge is a fit, buy with the same email and your box installs as the team you just designed — briefed for your business, priced the way you chose, ready the moment you add your key.