Seven guides sit here, each one written for a decision an owner has to make before anybody starts building: whether to automate, what to integrate, when custom software earns its place, how to plan a website, and how a business gets found in AI search. People at Mavrin Labs review all of them, and the editorial policy sets out how, including where AI tools help.
- Written for a reader who plans to do the thinking themselves
- Each one says when the answer is to build nothing
- Researched, reviewed and corrected in the open
- No reader counts, no download counts, no popularity claims
What the guides cover
The guides cover the four decisions that come up before any system gets built, plus the one that comes up afterwards. Readiness decides whether a workflow can be handed to software at all. Choice decides between an existing tool, a connection between tools, and something built for you. Planning decides what a website or an integration has to survive. Visibility decides whether buyers find the result. Each guide is a single page you can read in one sitting and act on without calling anybody.
Plan by the decision in front of you
The decision in front of you points at a shorter route than reading all seven. If you already know the symptom and want to see what a build would involve, the service pages describe the work itself. If you would rather start from the kind of organization you run and the way its week goes, the industry pages name the tasks first. Both routes end in the same place, which is one conversation about one repeated task.
- You know the symptom
- A task that repeats, records that disagree, reports that argue. The service pages describe each build.
- You know your sector
- Online selling, service work, nonprofit administration. The industry pages start from the week.
- You want the method
- How a target is agreed and checked afterwards. The measurable results method sets it out.
How the guides are kept honest
Every guide is held to the same rules as the rest of this site, which is why none of them carries a figure without a linked source and a checked date. No reader count or download number appears, because none is measured. Corrections are made on the page rather than quietly, and the review date changes when the content does. Where a guide describes an outcome that depends on systems Mavrin Labs does not control, it says so in those words.
A guide is published only when every fact in it can be sourced, which is why the library holds seven.
To turn any of this into a plan for your own systems, describe one repeated task through the contact page.
Frequently asked questions
Who writes and reviews these guides?
Guides here are reviewed by people at Mavrin Labs, the same people who build the systems the guides describe, and AI tools help with research and drafting before that review. Each page carries the date it was last reviewed, so you can see how current it is before you rely on it. The guides are written to be useful whether or not you ever speak to Mavrin Labs, which is why several of them reach the conclusion that a build is the wrong answer for now. The editorial policy sets out how a guide is researched, what counts as a source, and how a correction is made when something here turns out to be wrong.
Do you have to hire anyone to use these guides?
Nothing here needs an engagement behind it, and the guides are written for a reader who intends to plan the work themselves. Each one sets out what to decide, in what order, and which questions to put to any firm that offers to build the system, including this one. Several reach the honest conclusion that the simplest option is the right one and that no build is justified yet. Talking to Mavrin Labs makes sense in the other case: you have read the relevant guide, you know what you want to change, and you want a second reading of whether the hours inside it justify the work.
Last updated
Which hours would you take back first?
Send Mavrin Labs one workflow that is costing you the most time, and the reply comes back by email from the people who would build the fix.
Start a conversation