Custom software, inspection systems & websites — Perth since 2002
Practical notes on inherited software, internal tools, inspection workflows, websites, and software delivery that has to work in the real world.
If you are here because a system is brittle, the original developer has moved on, a spreadsheet workflow is getting out of hand, or your team needs a calmer way to improve software without a panic rewrite, start with the problem-led routes below.
Discuss a software problem Book an IHTMaps workflow review RSS Feed
The original developer is gone
You need takeover, safer releases, and a practical next owner for a business-critical system.
Spreadsheets became the workflow
You need calmer custom software, internal tools, or a staged fix to the system underneath.
Field inspections are too manual
You need better mobile capture, photos, maps, follow-up, and office handoff.
Fastest useful brief: "Here is the workflow or system that is slowing us down, here is what must keep working, and here is the first improvement we need in the next 1-3 months."
Send that brief if you want help choosing between takeover, workflow software, IHTMaps, or website redevelopment.
For businesses left with important software and no clear owner, support path, or calm next step.
For inherited systems where changes feel risky but the business still needs bug fixes, new features, and steadier delivery.
For teams that need tests, release guardrails, and calmer ownership before anyone talks about a rewrite.
For workflows held together by exports, manual re-entry, and too much staff memory.
Need a steady hand rather than another generic article?
Industrial Hypertext helps with custom business software, inherited-system takeover, workflow tools, inspection software, and staged modernisation work.
See inherited software takeover support or send the roughest possible brief.
What to Do When Your Original Software Developer Is Gone
A practical guide for businesses left with important software after the original developer has moved on, disappeared, or stopped supporting it.
How to Take Over a Business-Critical System Without Breaking It
A practical guide to taking over an important inherited software system carefully, reducing risk while still delivering fixes and improvements.
How to Make an Inherited Software System Safer Without Rewriting It
A practical guide to reducing risk in inherited software by adding tests, coverage, deployment discipline, and safer change habits before reaching for a rewrite.
When to Modernise a Legacy Business System Instead of Rewriting It
A practical guide to deciding when an older internal system should be modernised in place instead of replaced with a risky full rewrite.
Using Claude Code to Document Legacy Power Apps
A practical guide to mapping inherited Power Apps screens, flows, formulas, and dependencies faster with AI-assisted documentation.
When Spreadsheets Should Become Software
A practical guide to recognising when spreadsheet-driven workflows have outgrown their role and need proper software support.
From Dashboards to Dialogue: Why Operational Data Should Be Conversational
Most AI analytics is still polished reporting. The real shift is conversational reasoning over live operational data.
Turning Git History Into Client-Friendly Monthly Reports
How to turn a month of engineering output into a clear stakeholder-facing report without technical noise.
AI Portability Is Killing Stack Lock-In
Why faster translation across stacks changes software strategy, modernisation choices, and lock-in assumptions.
AI Agents Make Real-Time Stakeholder Prototyping Practical
Why tighter build-feedback loops can be better than long requirement rituals for internal systems.
OCLC WorldShare API Integration: How to Connect a CRM, Student System, or Library Workflow
A practical guide to OCLC WorldShare API integration, patron sync, SCIM users, and safer bridge architecture for real systems.
How to Use Agentic AI to Catch Up on a Busy Git Branch
A practical guide to turning a busy branch history into a clear, human-readable summary of what changed.
OpenClaw Is Not Just Another Chatbot
Why prompt-programmable workflows matter when you need automation in your own environment.
Why GitHub CLI Does Not Magically Fix Git Auth on Linux
A practical troubleshooting essay on why `gh auth login` can succeed while git clone still returns 403.
It's Not "Vibe Coding" If You Read the Diff
A quick note on how to keep speed while still applying judgment.
Original developer gone
You need takeover support, safer changes, and less delivery risk around a business-critical system.
Need mobile inspections, better field capture, photos, maps, and clearer reporting rather than another generic forms app?
If the real issue is weak enquiries, unclear messaging, or awkward technical ownership, the website may need a rebuild or calmer redevelopment path.
"Here is the workflow or system that is slowing us down, here is what must keep working, and here is what better needs to look like in the next 1-3 months."
That is enough to start a conversation about custom software, inherited-system takeover, IHTMaps, or website redevelopment.
Looking for the jobs product mentioned in some essays?
Need the next step, not another generic read?
Discuss a software bottleneck · Book an IHTMaps workflow review · Request a website quote
Best fit for inherited systems, spreadsheet-heavy workflows, internal tools, inspection processes, and websites that need better enquiry flow or calmer technical ownership.
Call 0432 000 583 if you want to talk through the current bottleneck directly.
E-business card (QR ready) for conferences and in-person shares. · Site map