Custom web application development. What to prepare for the first call
A practical process brief for a custom web app. Describe roles, inputs, exceptions and integrations before agreeing the scope and estimate.
In this article
In short
Prepare one process from start to finish before discussing a custom web application. Show the inputs, decisions and exceptions. A list of screens alone does not define the work the application must do.
Your spreadsheet has so many columns that new staff are unsure which ones they can edit. You want an application instead. What should you prepare for the first conversation?
Describe a complete task
Pick a repeated task. Explain what starts it and how someone knows it is finished. Remove customer details before sharing examples.
This example is a blank starting point for your own process. It does not describe a specific client project.
| Question | Example answer |
|---|---|
| What starts the task? | A customer sends an enquiry |
| Who enters the information? | Someone in the office |
| Who approves it? | The person responsible for quotes |
| What is produced? | An approved quote |
| What can go differently? | A missing attachment or incorrect details |
This gives the developer a job to understand. Button colours can wait.
Collect the exceptions
Can an approval be reversed? Who can see prices? What happens to a duplicate customer? Who handles a failed integration?
You do not need to design every answer yourself. Bring the cases that currently need a separate message or manual correction. They are useful material for a prototype.
List the systems that must stay
Name the sales, warehouse and accounting tools involved. Find out who holds administrator access and whether an API is available. Do not send passwords through an enquiry form.
The phrase warehouse integration leaves important questions unanswered. Which records move between the systems? Where is the authoritative version maintained? What happens when a transfer fails?
Agree what completion means
The scope should describe a working process and acceptance checks. Agree migration, backups, code access and ongoing maintenance as well.
Our custom web application service describes the work we cover. A prototype before payment lets you check the direction before production code.
Questions before the first call
Do you need a finished specification?
Not for the first call. Start with the process and real exceptions. The specification should follow the way the business works.
Is a custom application always necessary?
No. If an existing product supports the process without expensive workarounds, consider that option. We explain when a ready-made platform is better.
What should the first message include?
Tell us what you do manually, where the information lives and what should change. A technology shopping list can come later.
Can you start with one process?
Choose a process with a start and finish you can check. Preparing and approving a quote is one example. Agree which data must come from other systems. Other functions can be discussed as separate stages.
What should you check in a prototype?
Walk through an ordinary task and one error case. Check who can approve the result and what another person will see. A screen design does not establish that an integration already works.
What would you like to change in your business?
Leave your number. We will talk about your process and see whether we can help. The first call is free.
The service this text is about
Web applicationsWeb apps built around your process. Panels, systems and portals that run in the browser on any device.