Architecture, engineering and surveying
Tight fees, and hours that never reach an invoice
We build software for design, engineering and survey practices in Nelson Tasman. It links the hours, the changes to the brief and the council's requests to the fee, so you see where the work is going while you can still bill it. You make the design decisions and sign everything.
1 · Where the money and the hours go
Changes nobody writes up, and stages that run over the fee
A couple ask on Sunday what it would cost to open up the kitchen and add a family room. The fee proposal goes out a week after the first meeting, built from an old proposal and your memory of how long that job took. Halfway through developed design they ask to move the kitchen. You draw it, and nobody writes it up as additional services. Then the council's request for further information arrives, half of it for the engineer, and the clients ring to ask why the consent is still with council.
For an engineer, at the end of the build, it is the PS4 waiting on the builder's PS3s. For a surveyor it is a requisition, or a 224(c) the developer rings about every week. At month end the consent stage has used more hours than its fee covered.
This will not bring in more work, lower build costs or speed up the council. It shows you the hours going into changes and council requests while the job is still running.
What it is worth
What unbilled changes to the brief cost you
Use your own numbers, and count only the changes you would have charged for if someone had written them up.
a year
These are your own figures multiplied out: what unbilled changes cost you now. A client may not pay for every change.
2 · Automate the process
Watch a house alteration from enquiry to paid
A couple want to open up the kitchen of their 1970s house in Atawhai and add a family room. A small design practice takes the job from the website enquiry to the stage invoice matched in Xero, with a voice-over. You can also have one written for your own practice. The businesses, people and prices are made up.
- Enquiry: the clients send a project enquiry on the practice's website.
- Chat: the assistant takes down the address, budget and timing and books a site meeting.
- Project plan: the measure-up notes become a plan by stage, and the surveyor and the engineer are brought in.
- Fee proposal: drafted from past job hours, approved by the principal, then sent.
- Schedule: stage one is planned around the surveyor's and the engineer's days on site.
- Updates: a change to the brief is written up and signed, and the clients hear when the consent is lodged.
- Paid: the payment for the stage invoice, with the signed extra on it, is matched in Xero.
Try it yourself
Live demos set up for a design practice
Each demo opens on an example for a small architectural design practice. A version for your practice would use your own rules, fees and connections.
Project enquiries for a design practice
Ask a fictional practice about adding a room or a deck. The assistant takes down the address, budget, timing and any existing plans, and books a first site meeting. It will not say whether you need a consent or what the build will cost.
Try it as a design practiceA fee proposal by stage
Describe an alteration and get a draft fee proposal by stage, from measure-up to lodgement, with council and consultants' fees listed as exclusions. The hours are demo figures; yours would come from your own past jobs.
Try the fee proposalAn engineer's invoice coming in
A structural engineer's invoice to a design practice is read, checked and coded. One line does not multiply out, so it is held for someone to query. In a real build you decide what is charged on to the client.
Try the invoice inboxA day of site visits
Measure-ups, site meetings and an urgent builder query around Nelson Tasman, arranged into a day for the principal and the technician within each client's time window. Drive times are estimates, not live traffic.
Try the scheduler3 · Stand apart
Then add something the others do not have
These use your own timesheets, past RFIs, property files and site visits. They are ideas we can scope around your practice.
Fee proposals priced from your own past jobs
A new brief is matched with past jobs of the same kind (alteration or new house, floor area, sloping or flat site, which council) and the hours each stage really took on them. The fee proposal and terms of engagement are drafted in your template the same day. You set the fee, and it is only as good as your timesheets.
Your RFI history as a lodgement checklist
Every request for further information from Nelson City Council and Tasman District Council goes into one register, sorted by Building Code clause, building type and consultant. Before you lodge, the technician gets a checklist from your own list plus the items raised on similar jobs. It does not judge compliance or promise fewer requests.
Property file and title summary before the first meeting
The property file and the title you have ordered are read and summarised: past consents and plans, easements, consent notices and any hazard notes, each with its page number. You read it before the measure-up and the fee proposal, so an easement or consent notice turns up before the concept instead of at developed design. It is a reading aid, not a planning or legal view, and someone still checks the originals.
Site visit notes and photos that build the report
Photos and notes are taken on the phone against the construction monitoring or observation level agreed for the job, and site instructions and the builder's PS3s are logged as they arrive. The engineer's PS4 file, or the designer's observation report, is put together for the person who signs to review. It never signs or issues a producer statement, and it does not protect you from claims.
Getting started
A sensible first project
Start with changes to the brief on one kind of job, alterations say, and a few live projects. Run it for a few weeks and compare what it shows with what you already knew.
Changes to the brief
Additional services notes drafted for the principal to approve.
Hours against fee
A weekly view from the systems you already use, with a warning before a stage runs over.
Then invoices and RFIs
Stage or monthly invoices drafted from the fee proposal, then the RFI register.
Questions
Questions before you start
Do we have to replace our practice system or spreadsheets?
No. We start from the timesheets, job list and Xero you already use. If your system already shows hours against each stage, we use its figures and build only what is missing. If a system has no way to connect, we tell you before we build.
Will it check our drawings for Building Code compliance or tell us if we need a consent?
No. It builds a checklist from your own lodgement list and the items councils have raised on your past jobs. Compliance is the judgement of the person who signs the design, and the council decides on the consent.
Does it write or sign producer statements?
No. It gathers the site records, photos and the builder's PS3s so the file is complete when the engineer sits down to write the PS4. The engineer reviews and signs. Nothing is issued without a person.
Where are our drawings and client files kept?
In your own systems, or in storage we set up for you in an agreed place. Before we build, we agree what the software can read and which AI service it uses, and we check how that service treats what you send. Once it is paid for, the code and the data are yours.
See all industries · See all live demos
Related: Trades and property services · Professional services and clinics
Based in Nelson, working with businesses across Nelson Tasman and the top of the South. Meet the team