← All project planning notes

Project planning

How to scope your first enterprise web application

A practical starting brief for Ghanaian organizations: workflow, users, decisions and a rough timeline before a custom quote.

A custom web application should begin with the work your organization needs to do—not a long list of features. For Ghanaian organizations preparing a first brief, a clear account of the workflow is a useful starting point.

Describe the current workflow

Explain how the work moves today: who starts it, who reviews it and where delays or repeated entry occur. Use a general description; do not share confidential records, personal records or credentials.

Name the people and decisions

Identify the roles that need access and the decisions each person makes. For an approval workflow, for example, explain who submits a request, who approves it and what information each role needs. This is an example, not a Sanbra Hands client project.

Separate essentials from options

Write down what the first version must do, and keep useful later additions in a separate list. Mention existing systems that may need an integration. Authorization, access and third-party costs are dependencies to resolve before that work is agreed.

Give a rough timeline

You do not need a confirmed delivery date to inquire. Share the business event or planning window behind your need. A delivery timeline can only be confirmed after scope, dependencies and approvals are understood.

Agree what completion means

A written scope should describe deliverables, exclusions, milestones and acceptance criteria: the checks you will use to decide whether the agreed work is complete. It should also make handover and any support terms explicit.

Begin the conversation

Sanbra Hands builds custom enterprise web applications for Ghanaian organizations. Pricing follows agreed scope; there is no fixed-price package or instant quote. Submit your business need and rough timeline to start a scoping conversation, without creating an account.