Focused internal web app
Build a purpose-made tool when the important workflow does not fit an off-the-shelf product.
Useful for job intake, staff coordination, approval steps, evidence capture, reporting, client portals and operational dashboards.
Internal systems & managed platforms
A working system for the way your business actually runs.
Build a focused internal web app for a specific workflow, or configure, host and maintain an established open-source platform when that is the better fit.
Decision rule
Start with the operational result, not a predetermined technology. The recommendation may be a focused build, a managed platform or a smaller improvement to what already exists.
When it helps
The work is valuable. The admin around it is getting in the way.
This is for established service businesses with a repeated workflow, a clear owner and enough real work to judge whether the new system improves the day.
- Important work is spread across spreadsheets, email, messages and documents.
- People copy the same information between tools or repeatedly chase updates.
- An established platform could do the job, but it needs proper setup and ongoing care.
- The business needs a reliable technical owner without building an internal product team.
Two delivery routes
Build only what needs to be custom.
The goal is the most sensible working system for the business, not custom software for its own sake.
Managed open-source platform
Configure and run an established platform when the core capability already exists and a custom build would add unnecessary cost.
This can include setup, branding, hosting, updates, backups and ongoing maintenance. Moodle is one example for learning delivery.
How it works
A bounded route from messy workflow to working system.
01
Understand the workflow
Identify the repeated work, people involved, current tools and the result that needs to improve.
02
Choose the sensible route
Recommend a focused build, an established platform or a smaller change to the existing process.
03
Deliver a working first result
Agree the scope and success checks, then build or configure the smallest useful version around representative work.
04
Support it after launch
Add hosting, updates, fixes, monitoring and measured improvements only where continuing ownership is useful.
Relevant work
Evidence from real operational projects.
Purpose-built internal software and managed platform work, presented without exposing client records or technical infrastructure.
Scope boundaries
A focused first result, with the edges made clear.
- The first scope centres on one useful operational result, not replacing everything at once.
- The build-or-configure recommendation comes before a large implementation commitment.
- Content entry, specialist licences and third-party services are identified separately.
- Ongoing hosting and maintenance are agreed only where the system needs continuing ownership.
Start with the real work
Which workflow is taking too much effort to run?
Show the repeated process, the people involved and where the admin breaks down. You will get a practical recommendation for the smallest useful next step.