You don't need a technical document to start a custom software project. You need a clear picture of how your business works today and what is getting in the way. Here is what we ask clients to jot down before our first conversation.
The job, step by step
Pick the process that hurts most, such as billing, job cards or dispatch, and write how it happens today, from the first phone call to the final report. Include the workarounds: the Excel sheet, the WhatsApp group, the register on the counter.
Who does what
List the people who touch that process and what each of them needs to see. A counter clerk, a manager and an owner want very different screens.
The rules nobody wrote down
Approval limits, discount rules, which branch can do what. These usually live in someone's head, and they are exactly what off-the-shelf software gets wrong.
The reports you actually use
Bring the reports you look at every week, even if they are handwritten. If the software can produce them on day one, people will use it.
What a good first version looks like
Decide what must work at go-live and what can wait. Starting small and adding features in short rounds is faster and safer than building everything at once.
Bring these five notes to a call with us and the first meeting turns straight into planning, not questions.
