// Ideas
You don’t need a tech background. You need a starting point.
There’s probably something in your working day that could be simpler. Start there. Your first build doesn’t have to become a start-up.
You don’t need an app idea that changes the world. You need one thing you’re tired of doing the long way.
Maybe your customer information is scattered across messages. Maybe you send the same onboarding email every week. Maybe you keep forgetting who needs a follow-up. Those are perfectly good places to start.
Start with the bit that annoys you
Finish this sentence: “Every week, I have to…”
Then write down what happens now. Who starts the process? What information do they give you? Where does it go? What do you do next?
This isn’t glamorous. It is useful. A clear description of a real problem is a better starting point than a long list of features.
Build for one person first
That person might be you. A tool that saves you twenty minutes is still a tool worth building.
You could make a place to track enquiries, a simple project board or a checklist for preparing a client job. Keep the first version focused on one complete journey.
If you choose an enquiry tracker, that journey could be:
- Add an enquiry.
- Record what the person needs.
- Set the next action.
- See which enquiries need attention.
- Mark the enquiry as won or closed.
Leave invoicing, team management and automated marketing for later. First, find out whether the tracker helps.
Give your AI partner a proper brief
Don’t start with “build me an amazing business app”. Start with the work.
I run [type of business]. I need a simple tool to [one job]. Today I do this using [current process]. The first version is for [users]. Help me plan the main journey, the information we need to store and who should have access. Ask questions before building.
Your answers matter more than fancy prompt wording.
Try it with made-up information
Before you add real client details, use fictional records. Can you add something, edit it, find it again and understand what happens when a field is missing?
If people sign in, use separate test accounts. Check that each person can only see the information they should see. Ask for the data access rules to be checked too: hiding a button is not the same as restricting access.
You’re allowed to start small
The goal of your first build is to learn how an idea becomes a useful process. It can be rough. It can take a few tries. It can be only for you.
Choose the problem. Write the journey. Build the smallest complete version. Then use it.