Decision making
Should you rebuild or modernise your website?
A practical way to decide whether a rebuild is worth it, or whether focused modernisation creates more value with less disruption.
Read the guideCustom Internal Tools
Replace the spreadsheet with the system your team actually needs.
Businesses often adapt their work to generic software. When spreadsheets become the bottleneck, a focused internal tool can keep the workflow familiar while giving the team one reliable place to manage the work.
Typical outcomes
- One source of truth
- Fewer manual handoffs
- Less duplicate data
- Faster internal decisions
- Better operational visibility
Typical situations
Internal tools usually start with work that has outgrown its shape.
The problem is rarely a lack of software. It is usually a workflow that depends on scattered files, repeated updates and too much memory.
We have five spreadsheets tracking the same thing.
The team has the information, but nobody fully trusts which file reflects the current reality.
Our team copies information between systems.
Important work moves forward only after someone has retyped, checked or pasted the same data somewhere else.
Nobody knows which document is current.
Decisions slow down because the team spends time verifying context before doing the actual work.
Simple approvals happen in email.
Requests are easy to start but hard to track once decisions, notes and attachments spread across inboxes.
We lose time finding information.
The answer exists somewhere, but the path to it depends on who remembers where it was saved.
Reporting takes days.
The data is available, but turning it into a useful view still needs manual preparation.
Different departments use different processes.
Each team has adapted the workflow in its own way, which makes handoffs harder than the work itself.
One person understands how everything works.
The business keeps moving because one person knows the rules, exceptions and hidden steps.
Principles
Small systems should make internal work easier to run.
The aim is less friction, not more software.
One source of truth.
Important work needs one reliable place.
Remove duplication.
Repeated entry creates confusion.
Make work visible.
Status should be easy to see.
Reduce handoffs.
Context should travel with the work.
Automate where it helps.
Automate repeated work, not judgement.
Keep the workflow familiar.
Do not make the team relearn the business.
Build only what matters.
Build the smallest useful system.
Simple tools scale further.
Simple systems are easier to trust.
The work is organised around the bottleneck it removes.
Capability groups
A useful internal tool should simplify a real operation, centralise the right information and fit the way the team already works.
Information
Bring scattered operational knowledge into one place the team can trust.
Dashboards · Records · Document management · Searchable knowledge
Workflow
Turn repeated internal steps into a clearer path for requests, reviews and decisions.
Approvals · Requests · Forms · Operational processes
Reporting
Make progress, exceptions and operational signals easier to see without manual preparation.
Reporting · Analytics · Operational visibility · Exports
Integrations
Connect the existing systems that already hold important business context.
CRM · CMS · Accounting · APIs · Existing business systems
How I approach internal tools
The workflow is simplified before software is built.
Understand
Clarify the work people are trying to manage.
Map
Find the handoffs, data and decisions that create friction.
Simplify
Remove unnecessary steps before turning the workflow into software.
Build
Create the focused tool around the real operation.
Improve
Adjust the system once the team uses it in real work.
Common questions
Do we need to replace our existing software?
Not always. A focused internal tool can often sit beside existing systems and handle the workflow they do not support well.
Can internal tools connect to other systems?
Yes. They can connect to CRMs, CMS platforms, accounting systems, spreadsheets, forms and other business tools where integration is practical and useful.
Can internal tools be introduced gradually?
Yes. The safest path is usually to start with one workflow, prove the system is useful and improve from there.
Who owns the software afterwards?
Ownership should be clear before the work starts. The code, hosting, access and operating model should fit how the business wants to run the tool over time.
Can AI be included later?
Yes, if it helps the workflow. The better first move is often creating reliable data, clear steps and useful visibility before adding AI.
How large does a business need to be?
Size matters less than friction. A small team can justify an internal tool if repeated manual work is slowing decisions, customers or delivery.
Related insights
Practical writing that helps frame internal tools, automation and maintainable systems.
Technical strategy
Technical debt isn't always the biggest problem.
The visible problem is often the codebase, but the deeper constraint is usually decision quality, ownership or technical direction.
Read the strategy noteAI and automation
Where AI actually creates business value
A practical way to spot AI opportunities that reduce effort, improve consistency and make existing systems easier to use.
Read the AI insight
Make internal worksimpler to run.
Tell me which workflow is slowing the team down. We'll find the smallest useful system that makes the work clearer.
I'll personally review every enquiry and get back to you.
The best technical decisions usually begin with a conversation.
Get in touch