If the original developer or agency is gone, send the roughest possible brief. The first goal is to regain control, reduce risk, and move one useful improvement forward without a panic rewrite.
Response target: within 1 business day.
Best starting point: send a short plain-language brief. No polished spec required.
If the original developer is gone, the workflow is patched together with spreadsheets, or the system still matters but nobody feels safe changing it, do not overthink the brief. A commercially strong first enquiry usually only needs:
Low-friction start
Start on-page, send a pre-filled draft, or check the takeover support page first.
Email the brief
Best if you want to send the outline now and come back later with detail.
Use the quick form
Best if you want to stay on this page and send three details in one go.
Call about the system
Best if the workflow is urgent, fragile, or blocking current operations.
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.
IHTMaps inspection workflow review
Best fit for councils and field teams that need faster inspections, photos, maps, and reporting.
Website development quote
Best fit when the site needs clearer messaging, stronger enquiry flow, or calmer technical ownership.
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."
Most high-quality enquiries here already involve a real operational risk or bottleneck. That is enough context to shape the safest first scope quickly.
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."
Original developer is gone
"The original developer has moved on. The system still runs part of the business, changes feel risky, and we need help stabilising it while adding one useful improvement."
Spreadsheet-heavy workflow
"Staff are re-entering information across spreadsheets, inboxes, and PDFs. We need a calmer workflow and one safer first step without disrupting current work."
Legacy system still needs features
"Our older internal system still matters, but releases feel brittle. We need safer delivery, clearer ownership, and one overdue feature moved forward."
See inherited software takeover details
See when a spreadsheet-heavy workflow should become software
If the main problem is inspections, field reporting, or council workflow, the better route is usually an IHTMaps workflow review. If the main problem is website messaging or enquiry flow, use the website quote path.
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.
Lowest-friction option if you do not want to switch into your mail app first.
Inherited system stabilisation
Recover access, reduce release risk, and make the next change feel safe again.
Spreadsheet-heavy workflow fix
Replace awkward admin handoffs, re-entry, and reporting friction with a calmer internal tool.
Guardrails before bigger changes
Add tests, code coverage, CI/CD checks, or clearer deployment steps around a fragile area.
One overdue feature or bottleneck
Move one useful improvement forward without committing to a rewrite-first plan.
Three details are enough to start:
Inherited system: "The original developer is gone, the system still matters, what feels risky is [brief note], and the first improvement we need is [brief note]."
Workflow bottleneck: "Staff are currently doing [brief note] across spreadsheets, inboxes, or manual re-entry, what must keep working is [brief note], and we need [brief note] improved first."
Legacy modernisation: "The current system still works, but changes feel brittle, we cannot break [brief note], and we need [brief note] moved forward safely."
"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."
What you get back first:
Copy/paste brief template
You do not need to fill out every line. One or two concrete details is enough to start.
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.
Site map