Build - B2 Custom software and business systems
Custom software and tools
Software built for one business's exact problem, scoped and delivered in stages.
Request an introductionOverview
Custom software applications and internal tools built around your exact workflow, not a generic product bent out of shape. The work is scoped tightly and specified in writing before a line is built, which is what keeps custom software small, useful, and finishable.
The same team sets up the business systems around the build: CRM and office platforms matched to how you actually sell, and e-learning platforms for businesses that teach.
What is included (9)
- A written spec, agreed before the build starts
- The working tool: a web app or internal tool
- Admin and user access set up
- Handover and team training
- CRM setup in the HubSpot or Zoho class
- Pipelines matched to your sales process
- Core automations: routing and reminders
- For teaching businesses: an LMS with course and enrolment structure
- Payment flow and content upload support for courses
How it runs
Start with a diagnostic
We work out the exact problem the tool has to solve, and what it does not need to do.
Spec in writing
A written spec is agreed before build. The spec is the contract for scope.
Build in stages
You see working software in stages, not a reveal at the end.
Your review at each gate
Each stage is approved by you before the next begins.
Handover and training
Access is set up, your team is trained, and the documentation comes with the tool.
Where it starts
Starts with a diagnostic and a written spec. Nothing is built until the spec is agreed. That discipline is the service.
Questions
How does an engagement start?
With an introduction and a conversation. Tell us the problem first; we will tell you plainly whether this is the right service for it, and what it would take. For this service, it starts with a diagnostic and a written spec. Nothing is built until the spec is agreed.
How is the work priced?
Scope and price are agreed in writing, in an engagement letter, before work starts. Prices are set per engagement, because the work is custom. There is no checkout page, and there are no surprise invoices.
Why is a written spec needed first?
The spec is the contract for scope. It is agreed before the build starts, and nothing is built until it is agreed. That discipline keeps custom software small, useful, and finishable.
Does this cover CRM or learning platforms?
Yes, as part of the systems around the build: CRM setup with pipelines matched to your sales process, core automations for routing and reminders, and, for teaching businesses, an LMS with course and enrolment structure.
Related services
Custom automation
Business automation built with AI and workflow tooling: AI agents, n8n, OpenClaw, and Muse. The repetitive work in your business, connected and run reliably, with a human gate where it matters.
Web development
Design and build of websites and web tools, engineered for speed and kept lightweight.
Founder consultancy and planning
Working sessions and written plans for founders: what to build, in what order, and what to skip.