How to write a brief that gets your project started

Many good projects never start because the client thinks they need a perfect specification first. You do not. Every MasterFabric engagement begins with the brief, and a useful brief fits on one page.

What to include

• The problem: what is slow, manual, risky, or impossible today.
• The people: who uses the system, and who owns the result.
• The process: the steps people follow now, even if they live in email and spreadsheets.
• The data: where the information lives and who is allowed to see it.
• Done: what has to be true for you to call the project a success.
• Constraints: deadlines, budget range, regulation, or systems you must keep.

What you can leave out

Technology choices, screen designs, and architecture can wait. Those are decided in the planning step, together, once the problem is clear. If you already have preferences, mention them — but do not let them stop you from writing.

What happens next

Our process follows four steps: take the brief, plan with Claude, build in review, and prove and hand over. After the first conversation you get a plan for the architecture, the flows, and where AI belongs. Then the work moves in short, reviewed cycles until the software is tested, deployed, and yours.

A clear problem and a clear owner are worth more than a hundred-page specification.

Send it today

Use the contact form or write to info@masterfabric.co. Our working hours are Monday to Friday 09:00–18:00 and Saturday 10:00–16:00, Ankara time, and we aim to reply within one business day.