If you have an idea for an app, a system or a website, you might think you need a long technical document or complicated diagrams before meeting a development company.
You do not. All you need is a clear understanding of your business and the problem you want to solve.
At Alphabet we do not start with code. We start with understanding.
Explain the problem before you describe the solution
Instead of saying "I want an app", try:
"I want to reduce the time my sales team spends entering orders."
Or:
"I want customers to be able to book without calling us."
The clearer the problem, the easier it is to arrive at the right solution.
Know who will use it
Ask yourself whether the user is the customer, the employee, the manager or the supplier. Each has different needs, a different design and a different experience.
Describe how the work is done today
The process does not need to be perfect. But the development team needs to know how things work right now. For example: how do orders arrive? Who approves them? Who checks the invoices? How does payment happen? Where is the data kept?
Understanding today's reality is what lets us design something that fits your company rather than someone else's.
Set your priorities
Not everything belongs in the first version. Ask yourself which feature matters most, what can be added later, and what would deliver the most value if it launched first. This lowers cost and speeds up launch.
Have a rough budget in mind
You do not need a final figure. But a range helps us propose solutions that actually fit. What suits a startup is different from what suits a large company.
Do not worry if you are not technical
You are not expected to know programming languages or databases. The development company's job is to turn your business needs into the right technical solution. The better you explain the business, the better the solution.
Choose a partner, not just a developer
Ask the company:
- Do you start with a requirements study?
- Do you offer consultation before development?
- Would you advise me not to build an app if it is not necessary?
- Will I receive all the project files?
- How will the system be developed in future?
The answers tell you a great deal about how they work.
At Alphabet we believe technology should serve the business, not the other way round. Which is why we keep saying: sometimes the best solution is not an app.
Frequently asked
The follow-up questions we get most often on this topic.
Do I need to write out every detail before the meeting?
No. Explaining your business and the problem you want solved is enough — we will help turn that into clear requirements.
Do I need designs or wireframes?
No. The user experience can be designed once the project needs are understood.
Do I need to set a budget?
A rough range helps, so that the solutions proposed to you actually fit it.
What happens in the first meeting?
We get to know your business, your goals and the challenges you face, then discuss the best options available.
Will I get a price straight away?
It depends how clear the requirements are. Simple projects, sometimes. Larger ones need a study and analysis phase before an accurate quote is possible.