Internal operations
Winning the job is the easy part.
Everything after the job is won still runs through one person. That is where growth actually stops.
What we run on
- HighLevel
- HubSpot
- Xero
- Stripe
- Supabase
- Google Calendar
- Gmail
- Shopify
How you know
The business remembers nothing you have not remembered for it.
- 01Quotes go out when you get to them, not when the customer asked.
- 02The same customer exists in nine places and none of them agree.
- 03Scheduling happens in your head and in a group chat.
- 04You cannot tell which jobs actually made money until the accountant tells you.
- 05Onboarding a new person means three weeks of them asking you questions.
None of that is a people problem.
It is that nothing is written down anywhere a system can read it.
Everything on this page is included.
From $3,000 a month, sized to the business and what it actually needs. We work on a retainer rather than a fixed project price, because a project gets finished and paid for whether it worked or not. A retainer means we are still here when it needs changing, and still on the hook when it does not.
The front door
Every enquiry lands in one place and gets chased.
Not a CRM you have to remember to open. A place every lead lands automatically, with the follow-up already running before anyone has touched it.
CRM build and migration
One place every customer actually exists.
Most businesses have the same customer in four systems, each slightly different, and no agreement on which one is right. The cost is not the software, it is that nobody can answer a simple question without checking three places first.
What you get
- A single record per customer, with the duplicates merged rather than ignored
- Migration from whatever you are on now, including the spreadsheet nobody admits to
- Fields that match how you actually work, not the vendor's default template
GoHighLevel, HubSpot, or your existing platform
Pipeline and sales stages
Knowing what is about to close without asking anyone.
A pipeline is only useful if the stages mean something specific and everybody moves cards the same way. Most are set up once with the vendor's defaults and then quietly abandoned, which is why the forecast is always a guess.
What you get
- Stages defined by what has actually happened, not by how someone feels about it
- Separate pipelines per service where the process genuinely differs
- Aging rules so a deal cannot sit in one stage forever without flagging
CRM pipelines, per service
Lead capture from every source
Nothing arriving in a personal inbox ever again.
Enquiries come from the website, the phone, Facebook, a form, a referral and someone's mobile. If four of those land in a system and two land in a person, the two in the person are the ones that get lost.
What you get
- Every channel writing into the same place, including calls and social messages
- The database write happening first, so a failing integration never loses a lead
- Source recorded on every record without anyone typing it
Forms, call tracking, social inboxes, database-first capture
Automatic lead routing
The right person getting it immediately.
Speed of first response is the single biggest predictor of whether an enquiry becomes a job. Manual assignment means a lead waits for somebody to notice it, which on a busy day means it waits until tomorrow.
What you get
- Routing by service, region or workload rather than by who is looking
- Escalation if nobody touches it inside a set window
- Out-of-hours handling that does something other than nothing
CRM automation, notifications
Follow-up sequencing
Every enquiry chased, without anyone remembering.
Most enquiries are not ready to buy on the day they arrive. The business that follows up four times wins work from the business that followed up once, and the difference is almost never effort, it is a system.
What you get
- Sequences per service, continuing the conversation rather than broadcasting
- Stop rules so a customer who replies or books is never chased again
- Written to sound like you, not like a template
CRM workflows, email and SMS
Reactivation of old enquiries
Work out of the list you already have.
There is a list of dead enquiries in your system right now that cost you money to acquire and produced nothing. Most of those people still have the problem. Very few businesses ever go back.
What you get
- Old records segmented by what they wanted and how long ago
- Campaigns written to why they went quiet, not a generic check-in
- Run on a schedule rather than when things are slow
CRM segments, automated campaigns
Call and message logging
The whole history on the record, not in someone's phone.
Half the conversation with a customer happens on a mobile and never touches the system. Then that person is away, and nobody else can pick the job up without ringing the customer to ask what was agreed.
What you get
- Calls and texts logged against the customer record automatically
- Shared numbers so the business owns the conversation, not the individual
- Notes and files in one place instead of across three apps
Call tracking, shared inbox, CRM timeline
The front door
Every enquiry lands in one place and gets chased.
Not a CRM you have to remember to open. A place every lead lands automatically, with the follow-up already running before anyone has touched it.
Quoting
Priced before you leave the driveway.
The quote is where most small businesses lose the job. Not on price. On the three days it took to send.
Quoting and estimating apps
A quote out the same day, every time.
Quoting is usually the biggest single time cost in an owner-operated business and the one thing that cannot be delegated, because the pricing logic only exists in one person's head. Getting it out of their head is the whole job.
What you get
- An app built to your pricing logic, one decision per screen, priced as you answer
- Photos, measurements and voice notes captured on site rather than written up later
- Two documents out of it, a customer quote and an internal record with cost, margin and everything captured
Custom build, mobile first
Pricing calculators
Consistent numbers, whoever is quoting.
When pricing lives in a person, two people quote the same job differently and neither can explain why. That gap shows up as lost margin on the jobs you win and lost jobs on the ones you did not.
What you get
- Your rates, minimums, travel and variables encoded once
- Margin visible at the point of quoting rather than at the end of the job
- Updated in one place when your costs change
Custom calculators, internal only
Proposal generation
Documents that build themselves.
For anything more complex than a price, the proposal is a document somebody assembles by hand from a previous one, which is how last client's name ends up on this client's proposal.
What you get
- Generated from the record, so the details are never retyped
- Consistent structure, terms and inclusions every time
- Tracked, so you know when it was opened
Document generation from your own data
Acceptance and e-signature
Approved on a phone, not printed and scanned.
Every extra step between yes and signed is a chance for the job to stall. Asking someone to print, sign, photograph and email a document in 2026 loses jobs to whoever made it one tap.
What you get
- Accept and sign from the quote itself, on any device
- Acceptance writing back into the system and moving the job forward automatically
- A record of what was agreed, when, and by whom
E-signature, integrated with quoting
Delivery
The work moving without a meeting about it.
Once the job is won, the constraint stops being sales and starts being coordination. This is where most growth actually stalls.
Job and project management
Seeing the work instead of remembering it.
A whiteboard works until it does not, and the point it stops working is usually the point you hire the third person. Everything after that requires the state of every job to exist somewhere other than a conversation.
What you get
- Every job with a stage, an owner and a next action
- Photos, documents and notes attached to the job rather than emailed around
- Progress visible to the office without ringing the site
Custom build or your existing platform
Scheduling and dispatch
A calendar the whole business trusts.
Double bookings, forgotten jobs and the crew turning up to a site that is not ready all come from the same thing, which is a schedule that lives in one person's head and gets communicated by text.
What you get
- One schedule, visible to everyone, updated in one place
- Rules that prevent impossible bookings, like a cure time or a machine already out
- Changes pushing to the crew automatically rather than by phone call
Scheduling, calendar sync, mobile access
Inventory and materials
Stock levels that are true without a stocktake.
Typed stock numbers are wrong within a week. Derived stock numbers are right permanently, because completing a job writes the usage instead of asking somebody to remember to.
What you get
- Stock derived from movements, not typed over
- Usage written automatically when a job is completed
- Reorder flags before you run out on a Friday
Custom inventory, tied to job completion
Supplier workflows
Ordering that leaves a trail.
Materials ordered by text message are materials nobody can cost, chase or verify. It works at one crew and becomes a real cost the moment there are two.
What you get
- Orders raised against a job, so the cost lands where it belongs
- Confirmations and delivery dates recorded, not remembered
- Supplier pricing held in one place and updated once
Purchase orders, tied to job records
The work itself
Priced, scheduled and moving without a meeting.
The quote is where most small businesses lose the job. Not on price. On the three days it took to send.
Client facing
What the customer sees, and how easy you are to deal with.
Most of the competitive difference in a service business is not the work. It is how little chasing the customer has to do.
Customer portals
Customers who stop ringing to ask where things are at.
A portal is not a nice extra, it is an answer to the phone calls you are already taking. Every status update someone has to ask for is a cost you are paying and a signal you look disorganised.
What you get
- Job status, documents, photos and invoices in one place for the customer
- Access scoped so they see their own job and nothing else
- Updated by the system as the job moves, not by someone remembering
Custom portal, role-based access
Booking systems
A time confirmed without a phone call.
Anything that can be self-booked should be. The callback model assumes the customer is free when you are, and quietly loses every one of them who was not.
What you get
- Availability shown in real time, rules-aware, so nothing impossible can be booked
- Confirmations and reminders sent automatically
- Bookings writing into the same system as everything else
Booking, calendar rules, automated reminders
Customer onboarding flows
A first week that runs itself.
The gap between somebody signing and the work starting is where confidence is either built or lost. In most businesses it consists of three emails somebody writes from scratch each time.
What you get
- A sequence triggered by acceptance, covering what happens next and when
- Information collected once through a form rather than by back-and-forth
- Documents and access issued automatically
Automated onboarding, document generation
Review and referral capture
Proof collected while they are still happy.
The best moment to ask for a review is the day the job finishes, which is exactly when everyone is busy starting the next one. Automating it turns an intention into a system.
What you get
- Requests triggered by job completion, not memory
- Unhappy responses routed to you before they go public
- A referral path for the customers who would recommend you anyway
Automated requests, Google and industry platforms
Everything on this page is included.
From $3,000 a month, sized to the business and what it actually needs. We work on a retainer rather than a fixed project price, because a project gets finished and paid for whether it worked or not. A retainer means we are still here when it needs changing, and still on the hook when it does not.
What it adds up to
Four quotes went out before 7am. Nobody opened a laptop.
Two needed a decision and were waiting at the top of the list.
Money
Getting paid, and knowing what you made.
Most owners find out how a job went two months after it finished. The number existed the whole time.
Invoicing
Invoices out the day the job finishes.
Invoicing gets done in a batch on a Sunday because it is nobody's actual job. Every day between finishing work and sending an invoice is a day of your money sitting in somebody else's account.
What you get
- Invoices generated from the job record rather than retyped
- Triggered by completion, so nothing waits for a batch
- Matched to the quote, so variations are visible rather than absorbed
Xero, invoicing from your own records
Payments and chasing
Overdue accounts chased without an awkward call.
Almost nobody enjoys chasing money, which is why it happens late and inconsistently. An automated reminder is not rude, and it removes the part everybody avoids.
What you get
- Card and bank payment taken directly from the invoice
- Reminder sequence before and after due date, escalating on a schedule
- Payment status visible against the job, not just in the accounting system
Stripe, Xero, automated reminders
Job costing and margin
Knowing which work is worth doing.
Most service businesses know their revenue and their bank balance and almost nothing in between. The jobs that feel good and the jobs that make money are often not the same jobs, and without costing nobody finds out.
What you get
- Labour, materials and travel captured against the job as it runs
- Margin visible while the job is open, not after the accountant closes the month
- A view of which services and which customers actually pay
Job costing, tied to scheduling and inventory
The numbers
One set of numbers, current, without asking anyone.
Most owners find out how a job went two months after it finished. The number exists the whole time. It is just spread across four systems that never speak.
Data
One version of the truth, current, without asking anyone.
Everything above only works if the systems agree with each other. This is the layer that makes that true.
Internal dashboards
Seeing the business instead of remembering it.
A dashboard is not a report. A report is a thing someone builds monthly and everyone argues about. A dashboard is the current state, available whenever anybody looks, built from the same records the work runs on.
What you get
- The numbers that actually drive decisions, not everything that can be counted
- Built from your database, so every figure traces back to a record
- Working on a phone, because that is where it gets looked at
Custom dashboards on your own data
Database architecture
A foundation the rest can be built on.
The unglamorous part. Most small business systems are a set of apps that each hold a piece of the truth, which is why nothing reconciles. A proper database underneath means everything else reads from the same place.
What you get
- Schema designed around how the business actually operates
- Row-level security so people see what they should and nothing more
- Backups, migrations and history, so nothing is lost or silently overwritten
Supabase, Postgres
Integrations between systems
Systems that agree with each other.
Integration is the part that looks done and frequently is not. Platforms routinely return success while silently discarding data, which is why every connection has to be verified by reading the record back out of the receiving system.
What you get
- Every integration verified by reading the data back, not by trusting a success message
- Failures isolated, so one broken connection never takes the rest down
- Monitoring, so a silent outage is found in hours rather than months
Verified integrations across your stack
A single source of truth
One answer to every question.
When two systems disagree, somebody has to decide which one is right, and in most businesses that decision gets made differently every time. Naming one system as authoritative for each piece of data removes the argument permanently.
What you get
- One authoritative source per field, with everything else reading from it
- Sync direction defined, so nothing overwrites the truth
- Conflicts surfaced rather than silently resolved
Database-first architecture
Document generation
Paperwork that fills itself in.
Contracts, certificates, job sheets and compliance documents get rebuilt by hand from the last one, which is slow and is how errors propagate. All of it exists in the system already.
What you get
- Generated from records, so nothing is retyped
- Consistent templates, versioned, with the current one always used
- Stored against the job and available to whoever needs it
Document generation from your own data
SOPs and team onboarding
Hiring without three weeks of questions.
When the process lives in an owner's head, every new person learns by interrupting them. That caps how fast you can add people, regardless of how many you can afford.
What you get
- The processes that already exist written down where people work, not in a folder
- Checklists built into the system rather than sitting beside it
- Onboarding paths per role, so a new person is useful in days
Documented process, embedded in your tools
The work kept moving while you were away.
That is the entire point of building it this way.
What changes
Not how you work. When it happens, and whether it needs you.
A business that can run for a month without its owner is a business somebody would buy.
What it is for
He left. The lights stayed on.
Questions
Questions owners ask.
What does internal operations cover?
CRM, quoting, scheduling, invoicing, dashboards and integrations, built around how you already work. Everything after the job is won, which is where growth usually stops.
Do we have to change the tools we use?
No. We build around the tools you already use. Marketing on one side, internal operations on the other, connected in the middle.
What happens first?
We write your system down. How you price, who you chase, what makes a good job. Most owners have never seen it written down, and if nothing is documented the first phase is longer.
Who owns what you build?
You do. The accounts, the data and the code are all in your name from day one, and third-party software is billed to you directly so you can walk with it.
How is it priced?
From $3,000 a month, sized to the business and what it actually needs. How many systems, and how many people use them, are what move the number.
Where to next
Book a call
Show us what you already have.
One conversation. No deck, no pitch.
- 01We find the bottleneck. In time, in lost jobs, or in your own week.
- 02You get it in writing. What we would build, what it changes, what it costs.
- 03You decide. If it is not worth it, you still keep your system written down.
Tauranga, New Zealand · Working across New Zealand
info@nuggetai.co.nz