AI automation · AI-assisted SaaS

Automate the manual work. Ship the product around it.

Agentic AI workflows that replace manual admin, production SaaS shipped fast, and MCP integrations into the tools you already run, with human oversight on every step and tiered model selection that keeps costs honest.

Agentic workflows MCP integrations AI-assisted SaaS Tiered model selection
15+ years shipping product for
01 Outcomes
Per client / month
00h
Admin hours saved per month, per client, measured on the Northgate AI workflow programme.
Tiered model spend
00%
Lower ongoing AI spend with tiered model selection vs. routing everything through one premium LLM.
Kick-off → live
00 wks
From kick-off to a live MVP (automation or SaaS), without the agency timeline.
02 What we do
Capabilities

Built around AI, finished by senior craft.

Four services, one team. AI does the heavy lifting; a senior lead reviews every output before it touches your business. Nothing ships without human sign-off.

Core service

AI Automation & Agentic Workflows

Autonomous agents that replace stitched-together Zapier or Make rules. Tiered model selection, MCP integrations into Outlook, Xero, SharePoint, CRMs, judgment, not just triggers.

ClaudeGPT-4Open-weightMCP
Explore
Build

AI-Assisted SaaS Development

Idea to production SaaS without agency overhead. Spec, architecture, then AI-assisted delivery on cost-optimised infra.

Next.jsSupabaseVercelStripeClerk
Spec → live in weeks Explore
Strategy

Workflow Strategy & MCP Integrations

Audit current-state workflows, prioritise the painful ones by pain and payoff, then architect the agent fabric and MCP connectors into the tools you already run, Outlook, SharePoint, Xero, CRMs.

Workflow auditTiered model planMCP designGuardrails
Explore
Under the hood

A real agent config, not a marketing diagram.

Every workflow ships with a versioned config: which model handles which step, which MCP servers it can talk to, where guardrails live. Boring is good. Boring is auditable.

~/agents/variation-handler.toml
# tier the work, frontier model only when judgment matters
[agent]
name      = "variation-handler"
goal      = "draft variations, update finance, await review"
guardrail = "never_send_without_human"

[steps.reason]
model = "claude-opus-4"
input = "inbox.email"

[steps.draft]
model = "open-weight/llama-3-70b"
tools = ["sharepoint", "xero"]

[mcp.servers]
outlook    = "mcp://office365"
sharepoint = "mcp://sp.northgate"
xero       = "mcp://xero.payables"
03 How we work
Process

Map. Architect. Ship.

A short, honest loop. We start in your real workflows, choose the right model on every step, and put a working system in front of users fast, then keep tightening the loop.

01

Map the workflow

We sit with the people doing the work. Quotes, claims, support tickets, ops handoffs, we map current state, find the steps that break, and rank them by pain and payoff.

WorkshopsProcess mapPain · payoff matrix
02

Architect with the right model

Frontier models for reasoning, open-weight models for routine drafting, plain rules for calculations. MCP connectors plug AI into the tools you already pay for, no rip-and-replace.

Tiered model planMCP designGuardrails
03

Ship lean, measure, iterate

AI-assisted development takes us from spec to a production SaaS or site fast. We measure hours saved, error rate and cost per task, then keep tightening the loop.

Production deployHours savedCost / task
04 Capability snapshots
Recent work

Two snapshots of AI process work in the wild.

One on a working business replacing manual admin with autonomous agents. One on a green-field SaaS shipped on AI-assisted delivery.

AI Automation · Northgate

Nine workflows, one agent fabric for a Sydney luxury builder.

We mapped the nine workflows that run the business, quotes, variations, progress claims, supplier comparisons, site meetings, permits, subcontractor coordination, client updates, handover docs, and replaced the worst three with agentic workflows.

PM reads variation email
Cross-checks against quote v3 (manually)
Drafts variation doc in Word
Updates Xero invoice line
Replies to client · waits
Time per variation~22 min
Touches per week30+
Admin hours / mo~40h
PM reads variation email
Agent reasons over scope & pricing impact
Drafts variation doc + updates Xero (MCP)
Reply ready · PM reviews and sends
Time per variation~3 min
PM actionreview only
Confidence98%
Northgate Building Group platform
9Workflows mapped
160–300hSaved monthly
6+Tools via MCP
SaaS · AI-assisted delivery

Idea → spec → production SaaS, without an agency timeline.

Business analysis, user flows and functional spec come first; then architecture and stack picks tuned for cost, Next.js, managed Postgres, edge functions, Stripe, Clerk. AI coding tools accelerate build under senior review, so clients get a production-grade SaaS in a fraction of a traditional agency engagement.

Traditional timeline
15+ yrsSenior oversight
Full stackSpec → infra → live
05 Stack
Tooling

The tools moving the field forward, wired into your business.

We pick from the same shortlist serious AI teams use today, and tier them by cost so the ongoing spend stays predictable.

Layer 01AI models & protocols
Claude GPT-4 Open-weight LLMs MCP · Model Context Protocol Claude Code Function calling
Layer 02Automation & integrations
n8n Make Zapier Outlook · SharePoint Xero Go High Level Wunderbuild · Cubit
Layer 03Product & infrastructure
Next.js Node · Python Supabase · Postgres Vercel Stripe Clerk · Auth0
06 What clients say
We came to David for a website. He quickly showed us we were missing big opportunities beyond that and walked us into a smarter strategy. The workflow audit alone changed how we run admin, variations and progress claims that used to eat days now happen with the agent doing the heavy lifting.
JB
Jordan B. · Northgate Building Group
Sydney · AI Automation engagement
Senior thinking from the first call. We got a spec that actually held up under engineering review and a SaaS in production in a fraction of the time other agencies were quoting, without the usual hand-waving about "AI accelerating things."
DS
Daniel S. · SaaS founder
Melbourne · AI-assisted SaaS build
07 FAQ
Questions we hear often

Straight answers, no buzzword bingo.

What is an agentic workflow and how is it different from Zapier or Make?
Traditional automation links triggers to actions in a straight line. Agentic workflows give an AI agent a goal, the right tools and the autonomy to handle judgement, exceptions and multi-step reasoning, so you can replace stitched-together rules with one autonomous worker that you can actually trust.
How do you keep AI costs under control?
We tier the work. Frontier models like Claude or GPT-4 only run on tasks that genuinely need reasoning. Open-weight models cover routine drafting and normalisation. Pure rules and scripts handle calculations and reminders. That tiering typically cuts ongoing AI spend by 60–80% versus piping everything through a single premium model.
Can you build a SaaS end to end with AI-assisted development?
Yes. We move from business analysis to functional spec to architecture before any code is written, then use AI coding tools under senior review to ship faster than a traditional agency. Stack picks favour cost-efficient infra: Next.js, serverless, managed Postgres, edge functions and Stripe.
How do you keep humans in control of the agents?
Every workflow ships with explicit guardrails and a human review step before anything is sent, posted or paid. Agents draft, reason and prepare, a person signs off. The config is versioned and auditable, so you always know which model did what, and where the limits are.
How fast can an automation launch?
Lean engagements run 4–6 weeks from kick-off to live, whether that's an agentic workflow or an MVP SaaS. Larger builds compress traditional agency timelines roughly in half thanks to AI-assisted delivery under senior review.
Let's build

Pick the workflow that hurts most.
We'll ship the agent.

30-minute call, no pitch, bring a workflow, a SaaS idea, or a website that's not pulling its weight. You'll leave with a sharp opinion and a sketch of what we'd build next.