Statement of Work · ProjectCRON-P-001

Statement of Work for Cronulla Pools

For Cronulla Pools

Neighbourhood leadAlex BaileyPM + Builder
Prepared13 May 2026
Investment$30,048 ex GST
Reference until12 June 2026
StatusExpired
Your project at a glance

The whole engagement, on one card

Full detail follows below. This is the orientation.
Project codeCRON-P-001
EngagementFixed-scope project
Duration~11 weeks -- 13 May to 26 July 2026
Investment$30,048 ex GST -- paid in full prior to kickoff
Phases7 (process map + 6 build workstreams + wrap)
Workshops2 -- process-mapping with Scott; content workshop with Scott + Kate
Estimated go-liveWorkstream by workstream; full handover week of 20 July 2026
Your NBH leadAlex Bailey PM + Builder
Operates underMaster Services Agreement, signed 21 April 2026
ExpiredDownload as PDFso you can circulate this internally
This Statement of Work expired on 12 June 2026. It can no longer be signed online. Contact your Neighbourhood lead for a re-issued version.
01

Let's get started

Kate,

Thanks for the kickoff this morning -- it was useful to walk the whole thing end to end with you and Scott. This Statement of Work is the project-plan side of what we agreed in the brief: who's doing what, when each phase lands, what we'll need from your team to keep it moving, and how we handle the bits where reality changes the plan.

The headline is unchanged from the brief: six workstreams of work plus a wrap, $30,048 ex GST, end-state is a sales engine that stops the post-quote ghosting, runs the nurture for you, and gives you the management view you've been flying without. The interesting part of this document is the how -- the week-by-week schedule, the dependencies we'll need from your side, the risks we've already named, and the shared playbook for change.

No signature on this one. The MSA is signed and the work is underway. Use this as the source of truth when you're checking what's coming, what's on hold for your input, or what we agreed in the room.

Yell if anything reads wrong.

-- Alex

02

Project summary

Cronulla Pools is moving from a fragmented, manual sales process -- generic PDF quotes, leads ghosting after pricing, multiple pipelines, no management visibility -- to an automated, branded, data-driven engine. Six workstreams turn the proposal into a conversational lifestyle-led asset, route call notes from PLAUD into HubSpot automatically, build objection-path nurture sequences that drive site visits, and give Kate the executive view she has been missing. The work targets ~39 hours/month of team time recovered, lower Meta cost-per-lead via CRM sync, and a measurable lift in post-quote conversion.

03

The crew

Who you'll be working with, what they're on the hook for, and who the escalation backstop is.

Neighbourhood
Alex Bailey
Alex Bailey
PM + Builder
Day-to-day delivery across design, build, training, and comms.
al@nbh.co
Trav White
Trav White
AI Solutions -- Development of AI Tool
Builds the AI side of the engagement (PLAUD pipeline, proposal builder, weekly summary). Escalation backup if anything stalls.
tw@nbh.co
Cronulla Pools
Kate Lainson
Owner
Decision-maker, brand and content sign-off.
Scott Galley
Sales
Workshop participant, day-to-day pipeline user.
Matt Lainson
Operations
Operations and context.
04

Goals

Post-quote conversion Stop the leads-ghosting-after-quote problem. The kickoff identified this as the single biggest sales bottleneck.

  • Metric: % of quoted leads who book a site visit within 21 days
  • Target: Baseline measured at pipeline go-live; +50% by end of marketing-workflows workstream

Win-rate lift

  • Metric: Quote-to-Won rolling 90-day win rate
  • Target: +5 percentage points by end of project

Team time returned

  • Metric: Hours/month recovered (proposals + call notes + admin)
  • Target: ~39 hours/month

Management visibility

  • Metric: Weekly Monday AI summary plus live exec dashboard
  • Target: Live from reporting workstream, delivered 8am every Monday, no login required

Paid-media efficiency

  • Metric: Meta cost-per-qualified-lead
  • Target: Baseline at FB Lead Ads launch; reduction target set with Stephen Wyber
05

Outcomes: before → after

The shape of the change in one table - where things sit today, and where they'll sit with NBH.

The “with NBH” column starts hidden. Tap “Show with NBH” to reveal it. It’s always shown in the downloaded PDF.

TodayWith NBH
Generic transactional PDF proposal -- here is what 800 bars of steel costsBranded conversational page on proposals.cronullapools.com.au with lifestyle framing and dynamic project photos
Manual phone -> email -> text follow-up. Leads ghostAuto-nurture by objection type (price, timeline, multi-decision-maker, rock, external builder)
Multiple fragmented pipelines, Hot stage as a manual workaround, inactive deals invisibleSingle 7-stage pipeline with auto-prioritisation and backburner 30-day resurfacing. Hot retired
PLAUD recordings reviewed manually, notes inconsistentWebhook polls PLAUD ~10-15 min post-call. Claude extracts key points, objections, tasks. Auto-attached to deal
BuilderTrend PDFs re-keyed into proposals manually (45-60 min per quote)Upload PDF -> Claude extracts line items -> branded proposal page in minutes
No management view. Kate flying blindLive exec dashboard plus Monday 8am AI summary email
No newsletterMonthly branded issue, segmented across leads and past customers
No lead scoringProgressive profiling plus 75/40 thresholds (Hot / Warm / Cold)
Untargeted Facebook ads, no CRM syncNative HubSpot lead ads plus custom audiences, lookalikes, and suppression lists
06

HubSpot subscriptions

Cronulla holds Marketing Hub Professional and Sales Hub Professional, confirmed at kickoff. No subscription changes are needed for this scope. HubSpot licence fees are not included in the project fee -- they are Cronulla's direct HubSpot subscription.

07

Solution expectations

What's included

Process Mapping with Scott (Week 1): 1-hour session to map Scott's end-to-end sales process.

Pipeline Restructure (Week 2): unified pipeline, 7-stage structure, backburner resurfacing, inactive-deal detection, customised deal card, quote-review gate.

Marketing Workflows + Copy (Weeks 3-4): 1-hour content workshop with Kate + Scott, Alex drafts copy across all sequences (~26 emails), pre-quote sequence, 5 objection workflows, fallback workflow, brochure-download nurture, workflows connected and live.

PLAUD Call Notes (Week 5): webhook polling, Claude extraction, smart deal matching, review queue, rolling summaries, AI property fill, auto-tasks, weekly recap, team training.

AI Proposal Builder (Weeks 6-8): PDF upload trigger, line-item extraction, branded proposal pages, custom design, privacy-safe URLs, dynamic content, project showcase, brand video, two CTAs, engagement tracking, 30-day expiry, mobile responsive, HubSpot CRM card, photo library, post-proposal automations.

Newsletter + Lead Scoring + FB Lead Ads (Week 9): progressive profiling, 75/40 scoring, validation, FB Lead Ads, retargeting, Facebook custom audiences, newsletter template + first issue, content calendar, segmentation.

Executive Reporting + AI Weekly Summary (Week 10): Executive Dashboard, Activity Accountability Dashboard, Monday 8am email, AI Weekly Summary.

Across all workstreams: server hosting; integration documentation; team walkthroughs and handover; AI credits pay-per-use; bi-weekly check-ins; 2-week post-project QA window.

What's not included

  • Ongoing content creation past the first newsletter issue
  • Paid ads management (Stephen Wyber executes; we hand him the audiences and structure)
  • HubSpot licence and subscription fees (Cronulla's direct HubSpot bill)
  • Landing page design for the main cronullapools.com website
  • Refilling Claire's sales support role (deferred per decision log)
  • Photography and videography production (Cronulla supplies assets)
  • HubSpot SMS reply notifications (raised on the kickoff call as a possible addition; out of scope for this SOW; available as a future change request if needed)
08

Assumptions & dependencies

What this plan rests on. Each item names the assumption and, plainly, what happens if it doesn't hold - so a wrinkle is a conversation, not a surprise.

Workstreams run back-to-back with no gaps greater than one week
Re-queue adds 3-4 months to project end. Cost may increase if context has to be rebuilt.
Bi-weekly 30-min check-ins are honoured
Decisions stall, sign-offs accumulate, and workstream boundaries slip.
Cronulla holds Marketing Hub Professional and Sales Hub Professional (confirmed at kickoff)
Marketing workflows, PLAUD custom properties at scale, lead scoring + FB Lead Ads native, and custom reporting are blocked until upgrade.
PLAUD remains the call-recording tool
The PLAUD workstream needs a rewrite to swap to whatever replaces PLAUD.
Client supplies brand and content assets by the deadlines in section 19
Proposal-builder launch slips week-for-week with the late asset.
Stephen Wyber participates in the FB Lead Ads + audience handover
Audiences get built but sit unused. CPA-reduction goal becomes best-effort, not measured.
Kate is the single brand and content decision-maker
Each sign-off needs a broader sweep. Add 2-3 days per creative approval.
Ongoing infrastructure costs (dedicated server hosting and AI / LLM processing credits) are charged outside the project fee and capped by approval limits
We present an updated monthly forecast for your approval whenever projected spend would exceed the agreed cap ($250/month default). No surprise invoices -- you approve the limit before we run past it.
The week-by-week timeline is an estimate, not a fixed contract -- adjustments are recorded against this SOW as the project runs
Exact milestones, dates, and deliverable sequencing are confirmed at kickoff and updated in the live SOW page as scope, dependencies, or risk outside our control shift the plan.
09

Deliverables

  • Process map (Process Mapping workstream) -- Process-mapping session run with Scott; document shared with Kate.
  • Unified 7-stage HubSpot pipeline (Pipeline workstream) -- Pipeline live with entry criteria, required fields, backburner resurfacing, inactive grey-out, customised deal card. Old pipelines archived. Kate signs off.
  • Marketing workflows live in HubSpot (Marketing Workflows + Copy) -- Pre-quote + 5 objection paths + fallback + brochure-download nurture all live with Kate-approved copy. Auto-stop at Won/Lost/Contract/Backburner.
  • Email copy pack (Marketing Workflows + Copy) -- ~26 emails drafted by Alex, reviewed by Kate, approved before workflow go-live.
  • PLAUD -> HubSpot transcript pipeline (PLAUD) -- Live call appears on matching deal within 15 minutes. AI fields visible. Review queue functional. Scott trained.
  • Branded AI proposal page (Proposal Builder) -- Proposal renders at proposals.cronullapools.com.au/p/<hash>. Brand match. Mobile responsive. Two CTAs. Engagement tracking. 30-day expiry. Kate signs off on design.
  • HubSpot proposal CRM card (Proposal Builder) -- Card on deal shows upload status, extracted values, send-link, view count, post-proposal automations firing.
  • Project-photo library + upload tool (Proposal Builder) -- Kate can upload + tag photos. Library feeds proposal matched-project module.
  • Progressive profiling forms (Newsletter + Scoring + FB) -- Forms collect name/email/suburb first, then phone/pool type/timeline/budget.
  • Lead scoring model (Newsletter + Scoring + FB) -- 75/40 thresholds. Validated against closed-won deals. Hot leads create Scott task.
  • FB Lead Ads campaign (Newsletter + Scoring + FB) -- Native HubSpot integration live. Lookalike + retargeting audiences ready.
  • Facebook custom audiences (Newsletter + Scoring + FB) -- 4 audiences synced. Stephen confirms receipt.
  • Monthly newsletter, template + issue 1 (Newsletter + Scoring + FB) -- Template approved. First issue written, segmented, sent.
  • Executive Dashboard, Kate's view (Reporting) -- 5 tiles live.
  • Activity Accountability Dashboard (Reporting) -- Live for Scott + seat-replacement.
  • Monday 8am AI Summary email (Reporting) -- ~200-word briefing delivered every Monday 8am.
  • Full documentation + handover (Wrap) -- All integrations documented. Team walkthrough delivered. 2-week QA window opens.
10

Definition of done

When this project is “done”

The project is done when all 17 deliverables meet their acceptance criteria, Kate has signed off each workstream, the final walkthrough has been delivered, all integrations are documented, the 2-week QA window has opened, and the Monday AI summary has delivered successfully for two consecutive weeks.

  • All 17 deliverables meet their acceptance criteria
  • Kate has signed off each workstream per its approval gate
  • Final walkthrough delivered to Kate and Scott
  • All integrations documented (handover doc)
  • 2-week QA window opens (27 Jul to 9 Aug)
  • Monday AI summary delivered successfully for 2 consecutive weeks
11

Acceptance & sign-off process

How each deliverable gets from "we think it's done" to "agreed and signed off" - and what happens when something needs to change after that.

Workstream complete
Alex flags the workstream complete via email with deliverables and acceptance criteria checked off.
Kate reviews
Usually within 3 business days.
Approval given in writing
Email confirmation.
Next workstream opens
Decision logged on the live SOW page.
12

How changes are handled

Scope is what's set out in this Statement of Work. Anything beyond it follows the same steps - every time. No surprise work, no surprise invoices.

Raise in writing
Either side, via email plus a decision-log entry. Describe what and why.
Alex estimates impact
Hours, cost, schedule delta. Reply within 2 business days.
Kate decides
Approve, defer, reject. In writing.
If approved
Decision logged, schedule updated, change billed separately under the MSA at $310/hr ex GST.
13

Project timeline

The roadmap strip is the at-a-glance journey; the chart underneath is the detail - click any phase to see its tasks and approval gates. Dates are indicative and confirmed at kickoff.

Phase
W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
Runs Week 1 – Week 1

Lock in the foundation before any build work. 1-hour process-mapping session with Scott to map his end-to-end sales process.

Tasks & deliverables

  • Kickoff (13 May) -- complete
  • Confirm process-map session slot with Scott -- target Friday 15 May or Mon/Tue 18-19 May
  • Run the 1-hour process-mapping session
  • Document Scott's end-to-end sales process

Approval gate

  • No formal gate this phase.
Runs Week 2 – Week 2

One unified pipeline, seven stages with entry criteria, automated prioritisation, Hot stage retired.

Tasks & deliverables

  • Map current pipelines and consolidate
  • Define 7-stage structure with entry criteria and required fields
  • Backburner 30-day resurfacing logic
  • 14-day inactive grey-out and priority flag
  • Customise deal card
  • Quote-review gate
  • Decide deal naming convention (address-based recommended)

Approval gate

  • Sign-off on 7-stage structure + naming convention — by W2 (Kate)
Runs Week 3 – Week 4

Build the marketing collateral into the workflows. Alex drafts the copy, Kate reviews.

Tasks & deliverables

  • 1-hour content workshop with Kate and Scott
  • Alex drafts copy across all sequences (~26 emails total)
  • Pre-quote sequence (5 emails / 10 days)
  • Five objection workflows: Price/Value, Timeline/Council, Multi-DM, Rock/Site, External Builder
  • Objection-Type multi-select on the deal card
  • Fallback 3-email workflow
  • Brochure-download nurture (3 sequences, 9 emails)
  • Workflows auto-stop at Won/Lost/Contract/Backburner
  • Connect copy into the HubSpot workflows

Approval gate

  • Approve all email copy before workflows go live — by W4 (Kate)
Runs Week 5 – Week 5

Calls turn themselves into deal notes.

Tasks & deliverables

  • Webhook polling on PLAUD
  • Claude API extraction of key points, objections, action items, budget, pool specs, temperature score
  • Smart deal matching via title or contact name
  • Unmatched-recording review queue
  • Rolling deal summaries
  • AI-suggested property auto-fill
  • Auto-task creation
  • Weekly PLAUD recap (Mondays)
  • Team training on the naming habit

Approval gate

  • Sign-off on auto-extracted fields + review-queue UX — by W5 (Scott + Kate)
Runs Week 6 – Week 8

The proposal becomes the asset that closes the deal.

Tasks & deliverables

  • BuilderTrend PDF upload trigger to HubSpot
  • Claude extraction of cost groups and line items
  • Branded page at proposals.cronullapools.com.au/p/<hash>
  • Custom design matching the Cronulla site
  • Privacy-safe URLs
  • Dynamic content (client name, specs, cost breakdown, optional extras)
  • Completed-project showcase (3-5 by type then suburb)
  • Hero image
  • Embedded Kate/Matt brand video
  • Two CTAs (Accept e-sign / Book Call)
  • Engagement tracking
  • 30-day expiry
  • Mobile responsive
  • HubSpot CRM card
  • Project-photo library and upload/tagging page
  • Post-proposal automations

Approval gate

  • Sign-off on visual design + content sequence — by W8 (Kate)
Runs Week 9 – Week 9

Long-game lead nurture, scoring, and lead-gen.

Tasks & deliverables

  • Progressive profiling forms
  • Lead scoring model (75 Hot / 40-74 Warm / <40 Cold)
  • Score validation against closed-won deals
  • FB Lead Ads native HubSpot integration
  • Retargeting audiences plus lookalikes plus creative recommendations
  • Facebook custom audiences synced + handed to Stephen
  • Branded monthly newsletter template
  • First issue written and sent
  • Content calendar and writing guide
  • Audience segmentation (active leads vs past customers)

Approval gate

  • Approve newsletter template + first issue — by W9 (Kate)
Runs Week 10 – Week 10

Kate gets the management view she has been flying without.

Tasks & deliverables

  • Executive Dashboard for Kate (5 tiles: funnel, source perf, days/stage, closing this month, rolling 90d win rate)
  • Activity Accountability Dashboard
  • Monday 8am email PDF snapshot
  • AI Weekly Summary (Claude) -- 200-word pipeline briefing
  • Delivery to Scott, Kate, Matt

Approval gate

  • Confirm priority metrics + recipients — by W10 (Kate)
Runs Week 11 – Week 11

Final walkthrough, documentation handover, QA window opens.

Tasks & deliverables

  • Full team walkthrough (Kate + Scott)
  • Documentation finalised
  • Two-week QA window opens (27 Jul to 9 Aug)

Approval gate

  • No formal gate this phase.
Client actionsyour homework, on the same timelineW2Sign-off on 7-stage structure + naming convention · by W2W4Approve all email copy before workflows go live · by W4W5Sign-off on auto-extracted fields + review-queue UX · by W5W8Sign-off on visual design + content sequence · by W8W9Approve newsletter template + first issue · by W9W10Confirm priority metrics + recipients · by W10
Phase work Milestone (workshop / go-live / wrap-up) Approval gate — your sign-off

This timeline is an estimate. Exact milestones, dates and deliverable sequencing are confirmed at kickoff and recorded against this Statement of Work.

As the project runs, the dashed “you are here” line moves to the current week and the status badge near the top updates from “Draft · awaiting sign-off” to e.g. “Week 3 of 11· in delivery”.

14

Decision log / open questions

The calls still to make, who makes them, and by when - so nothing falls through the gaps between workshops. Updated as the project runs.

What we need to decideWho decidesBy whenStatus
Sales support role (Claire) not refilled immediately; re-decide post-automation at wrapKate2026-07-26Open
Hot deal stage retires once auto-nurture replaces itKate / Alex2026-05-24Open
Pipeline structured by stages, not propertiesKate / Alex2026-05-13Closed
Bi-weekly 30-min check-in cadenceKate / Alex2026-05-13Closed
Address-based deal naming convention (subject to pipeline sign-off)Kate / Scott2026-05-24Open
15

Project governance

  • Bi-weekly 30-min check-ins (Kate + Alex, optional Scott).
  • Email for all async decisions, logged on the live SOW page.
  • Workstream approval gates documented per workstream -- Kate signs off before the next workstream opens.
  • Two-week post-project QA window: Alex fixes any defects raised by Cronulla's team at no extra cost. Defects = does not match the acceptance criteria. New work = change request.
  • Change-control flow: any scope change > 4hr of work goes through the 4-step flow.
  • Status visibility: workstream progress and next-up reflected on the live SOW page at solutions.nbh.co/sow/cronulla-pools.
16

How we'll work together

The communication plan - every standing touchpoint, who's on it, what it's for, and what you walk away with. No mystery meetings.

Channel / meetingCadenceWhoPurposeWhat you get
Bi-weekly 30-min check-inFortnightlyKate + Alex (optional Scott)Status, blockers, decisionsDecision-log entries
Weekly async updateWeeklyAlex to Kate by emailWhat landed, what is next, what is blockedEmail update
Workstream-complete emailPer workstreamAlex to KateWorkstream sign-off triggerApproval reply
End-of-project reviewOnce, Week 11Kate + AlexWrap-up, QA window opensProject closure

Async channels

EmailAll formal communication and sign-offs
HubSpot dealTied to specific deals
PhoneKate-side escalation only
Two-way response-time commitment

Alex responds within 24 business hours on email and phone. Kate returns workstream sign-offs within 3 business days.

What we commit to each other

What you can expect from us
  • We do not ghost. Anything blocked is raised by email within 24 hours.
  • Decision log on the live SOW page is the source of truth.
  • Bi-weekly check-in is 30 minutes. Agenda shared 24 hours ahead.
What we need from you - and what happens if we don’t get it
  • Sign-offs returned within 3 business daysOr the timeline shifts
  • Brand and content assets supplied by the deadlines in section 19Or the phase slips week-for-week
  • Workshop attendance honoured (process-mapping in Week 1, content workshop in Weeks 3-4)Or workshops are deferred and the workstream pushes
17

Escalation ladder

If something isn't moving, here's the path - and how quickly you'll hear back at each step. Most things never leave step 1.

Level 1Alex Bailey -- al@nbh.co< 24 hours
Level 2Trav White, Head of Growth -- tw@nbh.co< 48 hours
Level 3MSA dispute-resolution clausePer MSA
18

Risk register

What could throw the project off course, how likely and how bad, and what we'll actually do about it. Click a row to see the plan.

How we’ll manage it: Branded conversational proposal and objection nurture directly target this. Add an indicative-extras line in the proposal.

Owner: Alex / Kate

How we’ll manage it: Pipeline prioritisation plus reporting dashboard surfaces stale deals.

Owner: Alex

How we’ll manage it: Pipeline + workflows + reporting designed to run hands-off. Re-decide at wrap.

Owner: Kate

How we’ll manage it: Client-requirement deadlines in section 19. Each delay documented in decision log.

Owner: Kate

How we’ll manage it: Loop him in at the FB Lead Ads workstream. Hand him audiences and structure; he owns execution.

Owner: Kate / Stephen

How we’ll manage it: Assumption explicit. Confirm by 18 May.

Owner: Kate

How we’ll manage it: Monthly cap and alert at $250 forecast.

Owner: Alex

How we’ll manage it: Review-queue UX and Monday recap nudges the habit.

Owner: Scott / Alex

Likelihood / impact pills: Low Medium High - click any row for the management plan and owner.

19

What we need from you

Your part of the deal

A few things from your side

This isn’t a disclaimer - it’s how the engagement stays on track. Each item names who’s best placed to provide it and roughly when we’ll need it, so nothing waits on a chase.

Scott available for process-mapping session (~1hr)ScottFri 15 May or Mon/Tue 18-19 May
Sign-off on 7-stage pipeline + naming conventionKateBy 24 May (pipeline)
1-hour content workshop attendanceKate + ScottBy 31 May (marketing workflows)
Sign-off on email copy across all sequencesKateBy 7 June (marketing workflows)
Scott available for PLAUD training session (~30 min)ScottWeek 5 (~8-14 June)
10+ recent BuilderTrend PDFsScottBy 15 June (proposal builder)
Brand assets pack (logo, colours, fonts, type)KateBy 15 June (proposal builder)
Kate / Matt brand videoKate / MattBy 22 June (proposal builder)
20-30 project photos for the libraryKateBy 22 June (proposal builder)
DNS access for proposals.cronullapools.com.auKate / MattBy 15 June (proposal builder)
Active HubSpot meeting link (Scott's calendar)ScottBy 22 June (proposal builder)
Post-acceptance workflow confirmationScottBy 29 June (proposal builder)
2-3 completed project case studies with photos + quotesKateBy 22 June (proposal builder)
Facebook Business Manager accessKateBy 6 July (FB Lead Ads)
Newsletter direction + first-issue approvalKateWeek 9 (~6-12 July)
Stephen Wyber loop-in for FB Lead Ads + audience handoverKateWeek 9 (~6-12 July)
Email + priority-metric confirmationKateWeek 10 (~13-19 July)
20

Who does what

A quick map of who's accountable for each workstream, who reviews and approves, and who's kept in the loop. Three states, not a full RACI matrix - enough to know where the buck stops without the bureaucracy.

WorkstreamNBH leadNBH delivery teamClient leadClient team
Build + technical implementationOwnsOwnsKeptInformedKeptInformed
Pipeline structure + namingOwnsOwnsReviewsReviews
Brand sign-off (proposal, newsletter)ReviewsReviewsOwnsKeptInformed
Content sign-off (email copy)ReviewsReviewsOwnsReviews
PLAUD recording habitKeptInformedKeptInformedKeptInformedOwns
BuilderTrend PDF supplyKeptInformedKeptInformedKeptInformedOwns
Project photo supplyKeptInformedKeptInformedOwnsKeptInformed
Brand video supplyKeptInformedKeptInformedOwnsOwns
DNS access (proposals subdomain)ReviewsReviewsOwnsOwns
Facebook Business Manager accessReviewsReviewsOwnsKeptInformed
Meta campaign execution (Stephen)KeptInformedKeptInformedReviewsKeptInformed
Newsletter ongoing (post-launch)KeptInformedKeptInformedOwnsKeptInformed
Decision authorityKeptInformedKeptInformedOwnsKeptInformed
Owns Accountable for getting it done.Reviews Reviews and approves the work.Kept informed Stays in the loop, no action needed.
21

Terms and conditions

This SOW operates under the Master Services Agreement signed 21 April 2026 (agreement reference msa_fixed). The full legal terms (IP, liability, confidentiality, termination, dispute resolution) live in the MSA and are incorporated here by reference.

Three protection lines

1. Work is done when it meets the acceptance criteria in the deliverable table. Defects raised inside the 2-week QA window are fixed at no additional cost. New work is a change request. 2. Scope is what's in this document. Anything outside the 17 deliverables and the 6 build workstreams is out of scope by default and handled via the change-control flow. 3. Client-side delays push project end dates. The 11-week timeline assumes the client-requirement items in section 19 arrive on time. Late assets and sign-offs slip the project week-for-week.

MSA extension -- Where this SOW conflicts with the MSA, the MSA prevails on legal terms; this SOW prevails on operational scope and timeline. IP transfers on full payment; confidentiality, liability, and termination are governed by the MSA.

Master Services Agreement

This Statement of Work operates under the Master Services Agreement signed 21 April 2026. The Master Services Agreement governs intellectual property, confidentiality, liability, termination and governing law.

IP in the deliverables transfers to you on full payment. Confidentiality, liability, and termination are governed by that Master Services Agreement - this Statement of Work covers the delivery; the MSA covers the legal terms.

22

Payment schedule

Project fee -- $30,048 ex GST ($33,052.80 inc GST)

Status: PAID -- paid in full prior to kickoff. No further invoices under this SOW.

Recurring add-ons (NOT included in the $30,048; billed separately):

  • Dedicated server hosting -- $85/month, billed annually
  • AI processing credits -- forecast ~$180/month at expected volume:
  • PLAUD transcripts ~$1.50/call (~$120/month at 80 calls)
  • Proposal generation ~$3.00/proposal (~$60/month at 20 proposals)
  • Weekly AI summary -- included

Change-request rate -- $310/hr ex GST (per MSA, applied to any approved change beyond this SOW's scope).

Pricing shown is ex-GST (AUD).

23

How invoicing works

When invoices land, what they're tied to, and what an overdue one means for the work. Short version: billing runs on its own clock, not the milestone clock.

The commercial triggers
  • Project fee paid in full prior to kickoff -- no further invoices under this SOW.
  • Recurring add-ons (server hosting, AI credits) invoiced separately on their own cadence.
  • Change requests invoiced on the next cycle after the change is approved in writing.
  • Any AI-credit top-up flagged at 80% consumption; client approves before the next batch.
Expired

This Statement of Work has lapsed

The signing window closed on 12 June 2026. Contact your Neighbourhood lead for a re-issued version with a fresh expiry.