The theory
Modern Growth+Ops Stack
Every build on this site runs on the same seven things. This page is what they are and why they are in that order. How I run the AI behind them is on the Operating Stackpage.
The seven
- 01
An owned site
A fast site on your own domain that you can change the same day you decide to.
Skip it · A page you cannot edit without asking somebody, on a platform that can raise its rent or close.
See it on Angelic Reiki → - 02
Conversion paths
One obvious way to book, apply or buy, and an owner who hears about it within minutes.
Skip it · Enquiries that arrive and cool. Most businesses lose more here than they lose on traffic.
See it on Angelic Reiki → - 03
Tracking and consent
Analytics and ad events that agree with each other, and a New Zealand privacy notice that says what is actually collected.
Skip it · Money spent on ads judged by clicks, because nothing downstream was ever wired up.
See it on Angelic Reiki → - 04
Booking and payments ops
The booking, the charge, the invoice and the receipt as one flow rather than four tools and a person retyping.
Skip it · A booking made somewhere else leaves no record, no invoice and no reminder. That is why there is one door.
See it on Angelic Reiki → - 05
An owned audience
An email list you hold, with consent, an unsubscribe and a real sender address.
Skip it · Selling a call to people who already booked one. A sequence that cannot stop is worse than no sequence.
See it on Feel Good Auckland → - 06
Reputation
Reviews and testimonials asked for the compliant way, after the visit, by email.
Skip it · A business with real happy customers and nothing a stranger can read. No quotas, no kiosks, no scripts.
See it on Nich Cycling → - 07
Attribution
The booked job and the paid invoice reported back to the channel that produced them.
Skip it · Cost per customer stays a feeling, so the budget follows whoever argues hardest.
See it on Creators Win →
Questions
- What is the Modern Growth+Ops Stack?
- A checklist for putting a small business on software it owns: an owned site, conversion paths, tracking and consent, booking and payment operations, an owned audience, reputation, and attribution. It is a way of working, not a product you buy.
- Which tools does it use?
- The surface is tool-agnostic and the plumbing is native: a Next.js site on Vercel, Stripe for payments, Resend for email, Google Workspace, and the platform APIs directly. Swapping the booking tool should not mean rewriting the business.
- Does it work for a business with no shopfront?
- Yes. The core is shared. A local business adds its map listing, its service and suburb pages and a post-visit review ask; an online-only business adds its apply or checkout funnel and its proof at scale instead.
- What is specific to New Zealand?
- The Privacy Act notice obligations, the Unsolicited Electronic Messages Act rules for email, and the fact that Google's Local Services Ads do not operate here. Search, Maps and Meta carry the load.
The tools behind it
The Operating Stack
How the AI side of the work is run: Notion as the memory, one skill library every AI shares, and the rules each session follows.