Read
We review the problem, operating conditions and obvious risk boundaries.
Start the signal map
Describe the work before describing the software.
A useful first message explains who is trying to do what, what gets in the way and what must be true for a first release to count as useful.
Your first brief can answer these questions
- What organisation, service or community does the project support?
- Who are the main users, and where and how do they use the current process?
- What is slow, fragile, confusing or impossible today?
- What would a useful first outcome look like?
- Which devices, connection conditions, languages and accessibility needs matter?
- Will the system touch personal data, money, regulated work or cross-border services?
- Who can approve the work and who will own it after handoff?
- What timing, budget range and existing systems should shape the first conversation?
What happens next
A decision, not an endless sales sequence.
Faith Forge Labs reviews the fit, identifies material unknowns and proposes a next step. That may be a discovery session, a bounded technical review, a first-build scope or an honest no-fit answer.
Clarify
We ask only for the missing details needed to choose a responsible next step.
Frame
If there is a fit, we document the scope, owners, evidence and acceptance path.
Ready to send the brief?
Use a clear subject line such as “Zimbabwe project brief” and include the non-sensitive answers you already know.