Guides — plain answers for businesses buying software
Straight guides for business owners deciding what to build, who should build it, and how to not get burned. Written by someone who ships and runs the software himself.
Practical guides for the decisions that come before the code: who to hire, what to build first, how much things really cost, and how to tell good work from expensive work. No jargon, no sales pitch.
How to choose who builds your app
A plain guide to choosing who builds your custom software — a freelancer, an agency or a studio. The questions to ask, the red flags to avoid, and how to compare cost, speed and who ends up owning the code.
ReadHow much does it cost to build an app?
What it really costs to build an app in 2026 — clear price bands for a simple app, a standard app and a complex product, what drives the cost, how long it takes, and how to spend less without wasting money.
ReadHow much does it cost to maintain an app?
What software maintenance really costs per year — clear price bands for apps and websites, what you're actually paying for, why it isn't optional, and how a build-and-run studio keeps ongoing costs predictable.
ReadHow to automate your business without hiring anyone
A practical guide to business automation for small and mid-sized companies — what to automate first, real examples (WhatsApp, orders, invoices, data entry), what it costs, where AI actually fits, and why no-code duct tape eventually breaks.
ReadIs it risky to depend on one solo developer?
The honest answer to the biggest fear about hiring a solo developer — bus factor, continuity, lock-in — and the three things that make depending on one person safe, plus why an agency isn't automatically less risky.
ReadAPI integration: connecting your business systems
What API integration services are, when you need one, common integrations (store, CRM, accounting, ERP, payments), off-the-shelf connectors vs custom, what it costs, and why an integration has to be kept running.
ReadWhere to find an experienced developer
Where to actually find an experienced software developer: 3 realistic places to look, and how to spot real experience before you hire anyone.
ReadHow to hire a developer you can trust
How to hire a software developer you can trust: ask to see 2-3 things they built and still run, get clear pricing, own your code, and check they stay after launch.
ReadIs this developer good? 5 green flags
How to know if a software developer is good: 5 green flags a non-technical person can check, from shipped apps to honest advice, before you hire.
ReadWhat to ask before hiring a developer
The 6-7 questions to ask before hiring a software developer: who owns the code, who maintains it, is the price fixed, what if it breaks, and can you see real work.
ReadI have an app idea, where do I start?
You have an app idea and don't know the first step. Here are 5 simple steps: name the problem, start small, get a real quote, and talk to someone who builds and maintains.
ReadWho builds custom software for small businesses
Who builds custom software for small businesses: the 3 kinds of builder — freelancer, agency, studio — what each is best for, and why a small studio fits most small businesses.
ReadHow long does it take to build an app?
Real timelines for building an app in 2026 — most apps take 8-16 weeks, bigger ones longer, and what makes a build faster or slower.
ReadWhat is a software studio?
What a software studio is: one team that designs, builds and keeps running your software, from first idea to years after launch. Compared to a freelancer and an agency.
ReadApp rescue — when your developer disappears
How app rescue works: recover your code and accounts, get the app assessed, and decide between fixing and rebuilding — a guide for non-technical owners.
ReadAdd AI to your business: start here
How to add AI to your business, step by step: start with one small task, skip the hype, and measure the hours saved. A plain guide for a small company, no jargon.
ReadOld, slow software: fix or replace?
Your software is old and slow. Here's how to tell if it can be sped up or repaired, or if it really needs replacing — usually without a risky full rebuild.
ReadCTO or senior developer?
Do you need a full-time CTO or just a senior developer? A plain guide for a non-technical owner, plus when a part-time or fractional CTO is the smarter, cheaper choice.
ReadYour lead developer left?
Your lead developer left and only he knew the system? A calm first-week plan: secure access, gather any notes, get the code mapped, and decide on a replacement later.
ReadIs my software secure?
Software security for owners who can't read code: the simple signs your software is safe, the warning signs it isn't, when to get a check, and what it costs.
ReadWhat is a technical audit?
What is a technical audit: a plain-language check-up of your software that shows what's fragile, what to fix first, and what it will cost, so you can decide with facts.
ReadWhy does it take so long?
Why software development estimates slip: the honest reasons, how to tell a fair delay from a red flag, and how to help your project move faster. Plain, no jargon.
ReadWho owns your code?
Source code ownership explained for owners: if you paid to build custom software, you should own the code. What to check, what the contract must say, and how to get access.
ReadDeveloper handover checklist
A developer handover checklist for non-technical owners: the access, code, plain notes, and contacts you must get so anyone competent can take over your software.
ReadWhat is technical debt?
What is technical debt? A plain guide: it's the hidden cost of shortcuts taken to build software fast. Some is normal, but here's how to spot when there's too much.
ReadAI with an old system?
Can you use AI with an old system? Usually yes. A plain guide for owners on adding AI to the software you already run, without a costly full replacement first.
ReadWhy is my site slow?
Why is my website so slow? The common causes of a slow website, why it costs you customers, and why fixing it is usually far cheaper than a rebuild. Plain, no jargon.
ReadIs your project in trouble?
The warning signs of a failing software project: no working demos, deadlines that keep slipping, answers full of jargon, and one person holding everything.
ReadManaging devs, non-technically
How to manage developers when not technical: ask for working demos, agree on outcomes, keep one clear owner, and listen for honest plain answers. A calm guide for a non-technical business owner.
ReadYearly software budget
How much to set for your yearly software budget: plan 15 to 25 percent of the build cost for upkeep, what it pays for, and how to keep costs predictable.
ReadIn-house or outsource?
In-house vs outsourcing software, made simple: the real trade-offs in cost, control, and speed for a small company, and when to hire, outsource, or mix both.
ReadIf your software goes down
What to do about software downtime when your app breaks on a Sunday: what going down means, who fixes it, how fast, and how to stop it happening again.
Read