Custom software, inspection systems & websites — Perth since 2002

Choose the closest-fit path

Custom software / inherited systems Takeover path

Best fit for inherited business systems, spreadsheet-heavy workflows, internal tools, and safer modernisation after the original developer or agency has gone.

  • business-critical software with unclear ownership
  • manual workflows patched together with spreadsheets and email
  • legacy systems that still need fixes, guardrails, and features

Inherited-system path selected

See takeover support

IHTMaps inspection workflow review

Best fit for councils and field teams that need faster inspections, photos, maps, and reporting.

Book workflow review

See inspection workflow page

Website development quote

Best fit when the site needs clearer messaging, stronger enquiry flow, or calmer technical ownership.

Request website quote

See website development details

Inherited-system shortcut: if the original developer or agency is gone, send the roughest possible brief anyway. The first job is usually stabilisation, safer changes, and regaining control — not a panic rewrite.
Best first move for most software enquiries

If the real issue is an inherited system, spreadsheet-heavy workflow, fragile release process, or internal tool bottleneck, skip the path-hunting and send the roughest useful brief below.

  • no polished spec required
  • best fit when the original developer is gone or changes feel risky
  • useful even if you only know the bottleneck, what must keep working, and the next improvement needed
Best-fit starting point: if you are unsure which path applies, start with the software enquiry. That is usually the right entry point for inherited systems, internal tools, workflow bottlenecks, legacy modernisation, and calmer technical ownership.
Most commercially useful software enquiries sound like this

You do not need to diagnose the solution. A short note about the current bottleneck is enough to work out whether the right first move is takeover, workflow software, stabilisation, or staged modernisation.

Original developer gone

The system still runs the business, but ownership is unclear and changes feel risky.

Open takeover path

See takeover support

Spreadsheet-heavy workflow

Staff are re-entering data, patching the process with emails, or relying on manual workarounds.

Open workflow draft

See when workflows should become software

Existing internal system needs work

You need bug fixes, safer releases, new features, or calmer ownership without a rewrite detour.

Open internal-system draft

Read the inherited-system guide

Good first brief: "Here is the workflow or system that is slowing us down, here is what cannot break, and here is the first improvement we need in the next 1-3 months."

Email that brief

Important: if the original developer is gone, the first step is usually stabilisation and control, not a panic rewrite or a long hiring process.

Start with the bottleneck that is costing you time or creating risk

You do not need a polished spec. A short plain-language note is enough to begin.

Fastest useful message: "Here is what is slowing us down, what must keep working, and what better should look like in the next 1-3 months."

Why these software enquiries turn into useful first scopes

The best-fit projects usually already have a real operational problem attached to them. That gives us enough context to identify the safest first scope quickly.

  • The original developer or agency is gone but the system is still business-critical
  • Staff are propping up the workflow with spreadsheets, inboxes, and manual re-entry
  • You need safer changes, bug fixes, and handover stability before any larger rewrite discussion
  • You need an internal tool, workflow system, or legacy modernisation project moved forward calmly
  • You want guardrails like tests, code coverage, deployment discipline, and clearer ownership
  • You need a practical fit-or-no-fit answer quickly, not a long sales process
What happens next: we identify the risky workflow or bottleneck first, then work out whether the right first move is takeover, workflow software, bug fixing, guardrails, or a broader modernisation plan.

See inherited software takeover details

See when a spreadsheet-heavy workflow should become software

If your problem is inspections, field reporting, or council workflow

That can still start here, but the better path is usually an IHTMaps workflow review rather than a generic software enquiry.

Book IHTMaps workflow review

See council inspection workflow details

What you get back: a quick fit or no-fit answer, the most sensible first step, and a realistic scope shape.

If you only send one thing, send this:

"Here is the workflow or system that is slowing us down, here is what must keep working, and here is what we need to improve over the next 1-3 months."

That is enough to start a software takeover, internal-tools, IHTMaps, or website quote conversation.

Custom software

Internal systems, workflow tools, business process improvement, and calmer technical ownership.

Inherited-system takeover

Stabilise legacy software, reduce change risk, and add improvements without panic rewrites.

Website or IHTMaps

Use the same contact path for website development quotes or council inspection workflow reviews.

Email: info@industrialhypertext.com

Phone: 0432 000 583

Send the brief here

Lowest-friction option if you do not want to switch into your mail app first.

Three details are enough to start:

  1. the workflow or system that is slowing the team down
  2. what must keep working while changes happen
  3. the first improvement needed in the next 1-3 months

Good enough: what is slowing the team down, what must keep working, and what improvement matters first.

Common first messages:

  • "The original developer is gone and we need a steady hand on the system."
  • "Staff are doing too much manual work around this workflow."
  • "We need changes, but we cannot afford to break the current process."
Useful if the original developer is gone: tell us what feels risky, what cannot break, and the first change you need next.

What you get back first:

  • a quick fit-or-no-fit answer
  • the safest first scope to move
  • a realistic view of takeover, workflow-tool, or modernisation options

Email Your Inherited-System Brief

Call 0432 000 583

See inherited software takeover details

Low-friction inherited-system brief
"The original developer has moved on. The system still works, but changes feel risky and we need help stabilising it while adding a few important improvements."

Email inherited-system brief

See inherited takeover support


1. Custom software / inherited systems

Best fit for business-critical systems, workflow bottlenecks, internal tools, inherited-software takeover, and safer modernisation.

See software takeover details

2. IHTMaps inspection workflow review

Best fit for councils and field teams that need faster inspections, cleaner reporting, and better evidence capture.

See council inspection workflow page

3. Website development quote

Best fit when the site needs clearer messaging, better enquiry flow, or calmer technical ownership.

See website development details

Copy/paste brief template

You do not need to fill out every line. One or two concrete details is enough to start.

What happens after you contact us
  1. We review your brief or call notes and confirm fit quickly.
  2. We suggest the most sensible first scope, with timeline and budget shape where useful.
  3. If the issue is urgent, we can start with a small first sprint or workflow review while broader scope is being finalised.
  4. We book a short call only when it helps move the job forward.

No hard sell. If we are not the right fit, we will tell you quickly.

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

Copyright © 2026 Industrial Hypertext - Software Development Perth, Western Australia | All rights reserved