In short
Describe outcomes and users rather than technical solutions, and let the developer propose how to do it. Ask for small, working pieces shown regularly, not a big reveal. Keep your code, domain and accounts in your own name. Ask questions in plain language, and judge progress by what you can actually use. If you need a second opinion on quality, pay an independent developer for a short review.
What you bring to the table
Developers know how to build things. You know the customers, the business and what success looks like. Those are the parts they can't get from anywhere else, and most failed projects fail through missing context, not bad code. Your job is to supply that context clearly and make decisions quickly.
Start with the problem, not the solution
Compare these two briefs:
- Weak: “Build a React dashboard with five charts and an export button.”
- Stronger: “Our account managers spend three hours each Monday collecting client numbers from four systems. We want that down to ten minutes.”
The second invites better ideas. A developer may tell you that a scheduled email with a spreadsheet would solve most of it for a fraction of the price. Our guides on how to write a website brief and how to write a product requirements document offer templates.
Include these in your brief:
- Who it's for, and what they're trying to do
- What's happening now, and why that's a problem
- What success looks like, in a measurable form if possible
- Constraints: budget, dates, systems you must keep, and legal requirements
- Examples of things you like, and what you like about them
Understand estimates
Software is hard to estimate, because much of the work is unknown until you start. So a sensible estimate is usually a range with assumptions, not a single number.
Useful questions to ask:
- “What would make this take twice as long?”
- “Which part are you least sure about?”
- “What could we remove, to ship in half the time?”
- “What's included, and what isn't?”
Be careful about pushing a number down without reducing the scope. You may simply be paying for optimism. Then you'll get the real number later, when it's more expensive. See how to estimate software development.
Ask for small, working pieces
This is the most useful thing a non-technical person can do. Ask to see something working every week or two, even if it's rough, on a staging link you can actually click. A staging environment is just a private copy of your site for testing.
You'll get several benefits:
- You can judge progress without reading any code
- Misunderstandings show up early, when they're cheap to fix
- You can change your mind, based on what you see
Be cautious if weeks pass with reports of progress, but nothing that you can see or touch.
Give good feedback
- Describe the problem, not the fix. “Customers can't tell whether their payment worked” is better than “make the button green”.
- Show what you did. A screen recording or a screenshot with the steps to reproduce saves a lot of time.
- Group your feedback. Send one list, not twenty separate messages.
- Separate bugs from new ideas. Something that doesn't work as agreed is a bug. A new thought is a change, and may affect scope and cost. See how to prevent scope creep.
- Name one decision-maker. If several people give conflicting instructions, the developer has to guess.
Decide quickly
Developers often pause because they need an answer from you. A slow decision can cost more than a wrong one, as you're paying for delay and lost momentum. Agree on a response time, and when you're unsure, ask: “What would you do, and why?” Most decisions can be changed later, so save your deliberation for the ones that can't.
Words worth knowing
You needn't memorise much, but a few terms help:
| Term | Plain meaning |
|---|---|
| API | How two systems talk to each other |
| Front end / back end | What users see / the server and data behind it |
| Git / repository | The history and storage of your code |
| Technical debt | Shortcuts that slow down future work |
| Deployment | Putting a new version live |
If you hear a term you don't know, ask. A good developer can explain anything in plain language. Reluctance to do so is a warning sign.
Protect your business
These steps don't require technical knowledge, and they prevent the worst outcomes:
- Own your accounts. The domain, hosting, code repository, analytics and app store accounts should be in your organisation's name, with your developer invited as a user.
- Get the code regularly, in your own repository, from the first week.
- Put it in writing. Scope, payment and ownership belong in a contract.
- Ask how you'd recover from a disaster. Who has backups? When were they last tested?
- Pay against delivered milestones, not just dates.
- Ask for documentation that would let someone else take over. See how to hand a project over.
If you ever have to chase your own logins, fix that first.
How to judge quality without reading code
- Does it work reliably, including on your phone?
- Are bugs fixed once, or do they keep coming back?
- Do small changes stay small? If each change takes longer than the last, that's a warning sign.
- Can your developer explain decisions in terms of your business?
- Are there automated tests, and do they run before each release?
For a second opinion, pay an independent senior developer for a few hours to review the code and give you a written summary. It's inexpensive compared with discovering a problem at launch. And if a developer strongly objects to this, take note.
AI changes the picture slightly
You can now use AI tools to explain code, translate jargon or check a proposal, which helps you to ask better questions. They're useful for a first look, but don't treat them as proof of quality. If you're building something yourself, see when to hire a developer after vibe coding.
If you'd like a technical partner who'll explain things plainly, book a call.
Common questions
How do I know if a developer is any good if I'm not technical?
Look at past work you can try, speak to former clients, and notice how clearly they explain decisions. Do they ask questions about your business? Consider paying an independent developer for a short code review once the work has started.
Should I learn to code before hiring a developer?
It isn't necessary. It's more useful to learn basic terms and how software projects run. Being able to write a clear brief, make decisions quickly and review working software will do more for your project than a beginner coding course.
How often should I meet with my developer?
A short check-in every week works for most projects, plus a demo of working software every week or two. Avoid daily interruptions unless you're in a critical phase. The goal is to see progress regularly and to remove blockers quickly.
What should I own when hiring a developer?
Your domain, hosting account, code repository, analytics, app store accounts and any third-party services should be in your organisation's name. The developer should have user access, not ownership. Get your contract to confirm ownership of the code and designs.