What should we discuss before building a business system?

Bring an existing spreadsheet or one real workflow. Explain who uses it, where it gets stuck and what completion should look like.
Discuss the workflow
View checklist text

Bring working examples

  • Sample records: bring spreadsheets, forms or business records, explain their fields and remove information that should not be shared.
  • One workflow: describe the steps from initiation to completion, including handlers, reviewers and points where work is repeated.
  • Existing tools: bring screenshots, system notes or available API documentation, with the current owner identified.

Define roles and operating rules

  • Roles and records: list who initiates, handles, reviews and views work, with the records each role needs to access.
  • Actions and exceptions: identify review steps and how returns, missing information and pauses should be handled.
  • Connections: identify information held in other tools, the required handovers and the interfaces and access available.

Agree the first scope and acceptance paths

  • Priorities: separate first-release essentials from later additions, with the main devices and working scenarios.
  • Data and checks: describe migration sources and historical retention needs, then choose records for normal and exception-path checks.
  • Launch and handover: agree the target timing, budget direction, operators, maintenance owner and required instructions.

Walk through one everyday task

Explain where a task starts, how it is handled and who receives the result. That gives a clearer starting point than feature names alone.

Where does it start?

Who starts the task, which materials are submitted and where are records kept? Use one working example.

What happens in between?

Put processing, review and handover in order, including returns and incomplete-information cases.

What result is needed?

Define completion, the records to retain and who needs to view or act on the result.

How do existing tools connect?

Identify source systems, interfaces, data owners and which information must be read or updated.

More questions to work through together

An incomplete specification is fine. Bring a real task and current materials, and flag what is still uncertain.

Can current spreadsheets serve as requirements materials?

Yes. Explain fields, typical records, calculations and who enters or reviews information. Include handovers and exceptions that happen outside the spreadsheet.

Should every feature be built at once?

Prioritise by frequency, business importance and dependencies. Choose a first release with complete working paths before planning further additions.

Let's talk about your project

Websites / Business systems / AI applications

Chat on WhatsApp