Straight answers before you spend money.
Each guide is a short summary of the questions we get asked most often, written for business owners rather than developers.
All guides
Six questions we hear every week.
Pick the topic closest to your situation — the linked service page has the full detail.
How to decide between custom software and off-the-shelf tools
A short framework based on process complexity, budget and how much your workflow differs from the standard.
Read in the Development guide WebsitesWhat a business website actually needs in 2026
The pages, performance targets and enquiry paths that matter — and the features that can wait.
Read in the Websites guide MarketingA realistic 90-day plan for local search visibility
Google Business Profile, on-page basics, reviews and content: what to do in which order.
Read in the Marketing guide Paid AdsHow to judge a paid ads report
The five numbers to check before you accept a performance report — and the ones that hide problems.
Read in the Paid Ads guide IT & CloudPreparing your IT setup for a growing team
Backups, access control, e-mail deliverability and documentation before you hire the next ten people.
Read in the IT & Cloud guide AI & AutomationWhich process should you automate first?
How to score repetitive work by frequency, error cost and measurability to pick a sensible first project.
Read in the AI & Automation guideKeep it simple
Three rules that save most projects.
Start with the process, not the software.
Write down how the work actually happens today — who does what, in which order, and where it slows down. Software that ignores this step becomes another thing to work around.
Buy the version one step ahead of where you are.
Systems that try to solve problems you do not have yet are expensive and get abandoned. Choose the smallest build that fixes today's bottleneck properly, then extend when the next one appears.
Agree on one number that proves it worked.
Enquiries per month, hours saved per week, error rate, cost per lead — pick one before work starts. Without it, every project ends in an opinion instead of a result.