Nothing saved yet

Build
brief.

Tell us what's slow. We'll tell you what's buildable.

This replaces the first two discovery calls. Fill it in with real numbers where you have them and rough ones where you don't. A guess you flag as a guess is more useful than a blank.

  • About 12 minutes. Saves in your browser as you go, so you can stop and come back.
  • Nothing leaves this browser until you send it. At the end you get a brief to copy, download, or send straight to us.
  • Describe the process, not the solution. Don't worry about which AI does what. That's our job.
01 / 06

Who we'd be building for.

So the brief has a name on it and we know who to call.

What do you need? * Tick everything that applies. This decides what we ask you next.
Who has to say yes before work starts? Tells us whether we're scoping with the decision-maker or preparing something they'll take upstairs.
02 / 06

What the agent handles.

An agent is software that answers and acts on its own, whether that is a conversation it holds or a job it just gets on with. The useful part is not what it can do, it is where it has to stop. Add the work it would take over underneath and we'll score what you get back.

The build

One line, the way you'd say it out loud.
The consequence, not the feature list. What can't you do today because it doesn't exist?
The spreadsheet, the WhatsApp group, the paper form, or nothing at all.
Who uses it? *
The main path, start to finish. Who opens it, what they put in, what comes out the other end.
The version you'd still switch to if nothing else got built.
Naming this early is what keeps the first version shippable.
Logins and permissions *
Where does it need to run? *
Systems it must read from or write into. The next step covers what you run on generally.
A product, a competitor, a screenshot. "Like X but for Y" saves us an hour of guessing.
Who looks after it once it's live?

The agent

The work you'd hand to a new starter on their first week.
Where does it work? * Where the messages or requests actually arrive.
Who is it dealing with? *
Who picks it up, how long it takes them, and what they have to go and look up.
Where the right answer lives today: the price list, the manual, past replies, someone's head.
The most important answer here. An agent that knows when to stop is the one you can leave running.
Does it need to change anything in your systems? *
A rough count is fine.
Tone, and any language it has to handle.
What the customer sees, and who gets told.

The work it would take over

Optional, and the most useful thing you can give us. One card per job that eats time, and we'll score each one on how much you'd get back against how cleanly it can be handed over. Skip it if you'd rather just talk.

The content

What are we making? * Advertising lives here too. Tick the ad formats and we'll treat the creative as part of the same job.
The job the content does. Filling a feed and selling a product are different briefs.
A rough number is fine. Volume is what decides whether this is worth automating at all.
Where does it go? *
Including "nobody, that is the problem". If it is outsourced, say what that costs.
The bit that stops it looking like everyone else's AI output. Tone, look, the words you always or never use.
What can we work from? * Whatever exists already. Feeding it your own material is the difference between your voice and a generic one.
Who approves it before it goes out? *
The output you would be embarrassed to see with your name on it.

The website

What kind of site? * Tick everything it has to be. Plenty of sites are two of these at once.
The main path, start to finish. Find a price, book a slot, buy a thing, check an order, or send an enquiry that reaches the right person.
A site you want replaced, a Facebook page doing the job instead, a builder site nobody can edit any more, or nothing at all.
A guess is fine.
Payments, bookings, stock, a CRM, your mailing list.
What do we have to work with? * Whatever already exists. Your own material is the difference between your site and a template.
A competitor, or any site you like the feel of. Saves us an hour of guessing.
Who updates it once it's live? * Changing a price or adding a page. Say if nobody has been given the job yet.
Says more about the build than a feature list does.
03 / 06

What it plugs into.

Integration is where builds slip. The messier the honest answer here, the more useful it is.

Tools the business runs on * Tick everything that touches the work above.
The records the work depends on: customers, orders, prices, stock, cases. Say if it's split across places.
Can you get that information out? *
Could you share a real sample with us? * Twenty real records beat a hundred clean fake ones. Real data is where the edge cases hide, and we'd rather hit them in week one than week eight.
04 / 06

What we have to work around.

The things nobody mentions until week three.

Rules on the data
A band, not a commitment. It decides whether we scope one build or a phased one.
Including "nothing". If something failed, what broke: the tool, the training, or the follow-through?
Says more about the design than any feature list.
05 / 06

How we'll know it worked.

One number, agreed now. Every later "can it also…" gets measured against it. That's what keeps a build from turning into a wishlist.

Be specific. "Quotes go out same day instead of in three days." "Nobody touches the invoice inbox on Mondays."
A rough figure is fine. Say if you're guessing. Without a starting point there's nothing to compare to later.
Where the system should stop and hand over. Everyone has a line here; naming it early keeps it in the design.
06 / 06

Your brief.

Everything you've told us, in the order we'd work through it. Send it over and we'll come back with a scope, not a sales call.

Sent.

It's in the inbox at Forged One. We read every one properly. Expect a reply within two working days, with a scope rather than a sales call.

Your answers stay in this browser so you can send an update later.

Where this goes: your answers leave your browser only when you press Send, to a Forged One inbox, by email. Nobody else is copied and it is not sold or shared. The chat assistant relays what you type to it, and nothing from the form, to a model host. Ask us at forgedonebusiness@gmail.com to delete anything you have sent, and we will sign an NDA before any real data changes hands.

Sending puts the brief straight in front of us, attached as a file. Prefer to keep it in your own hands? Copy or download it and email forgedonebusiness@gmail.com yourself.

The exact text we receive