Cover1 / 12
Platform Business Thesis

Build on Agend.

The conduit between any system of record and any front-end you want to build. Growth without projects. The product is the offer.

THESIS  ·  Owner Glen  ·  8 July 2026  ·  Build on Agend strategy arc
The thesis in one paragraph

Agend is the platform, the conduit between whatever system of record a client has and whatever front-end they want to build. Clients get a documented API, a widget library, a portal, workflows and their own data models. They bring their own design team, their own website, their own agency. We can be their everything, but we don’t have to be, and that optionality is the product.

Growth stops requiring projects, because the project is done by the client. Our onboarding onboards them to the platform, not to a bespoke website build.

The Platform Business Thesis
The coming-together

Five pillars

1

Minimise Upbeat friction

Reads serve from our hub at our speed, so years of the platform’s worst operational pain, the whole async and hardening arc, are structurally deleted. Traffic routes through our API, not theirs.

2

Maximise client advantage

The engagement layer makes a client’s existing CRM investment better while making us the surface everything runs through.

3

Minimise duplicated effort

No new WordPress plugin per client, no per-client portal, no WooCommerce. The difference between Agend Pro and any suite client’s site becomes minimal to nil.

4

Growth without full-service delivery

Widen the net on supported front-ends. The client’s team or agency builds, while we supply keys, widgets, docs and rails.

5

Focus

The product is the offer. Wins come quicker because engineering effort compounds in one place instead of dispersing across bespoke builds.

One place to improve. Every client benefits at once.

Five pillars
What it unlocks

Four strategic moves

Headless by default

Same key, same widgets, same API, any host.

The widget library mounts on data-widget divs. WordPress is merely the first host. Squarespace, Webflow, a custom Next.js build or a kiosk all run the same key, so the market widens from “associations on WordPress” to “associations with a website”.

Growth without projects

Revenue scales with keys issued, not hours billed.

Onboarding becomes a repeatable platform activation instead of a subjective website project. This is the agency to software-company transformation, stated plainly.

The Learn partner play

The Trailhead playbook.

Use Agend Learn, our own LMS, to train agencies and client dev teams on the platform, certify them and badge them. The training material is itself a demo of the product. This is how Salesforce built an ecosystem, gained here by dogfooding.

The multi-CRM wedge

Upbeat is source #1, not the ceiling.

The driver architecture already exists (GenericAdapter and GroundhoggAdapter). It points at Salesforce, Zoho, Membes and iMIS, arriving as the engagement layer where migration becomes the client’s own idea later. Succession with coexistence, generalised to every AMS and CRM.

Four strategic moves
What exists today

More is real than the roadmap implies

Of the 11 platform primitives a client needs to build on Agend, five are already shipped and four more already exist internally. Only two are true greenfield, and both are policy and plumbing, not new product.

01Public versioned API, scoped keys, entitlementsShipped
02Webhooks, signed and replayableShipped
03SSO and embedShipped
04Metered billing on API usageShipped
05Sandbox (ag_test_ keys)Shipped
06Client-side components (widgets)Half
07Workflows for clients (visual DAG)Internal
08Data extensibility, custom objectsSized
09Platform contract (SLA, changelog, SDKs)To build
10External-tenant hardeningGated
11AI and agent surface (MCP)Internal
5 / 11
primitives already shipped
4
more already exist internally or half-built
2
true greenfield: contract & hardening
Readiness scorecard  ·  5 shipped · 4 half · 2 missing (of 11)
Keeping it honest

Three conditions that keep the thesis honest

The revenue bridge

Project revenue winds down while platform revenue ramps, and it only works if the curves cross in time. Pricing and packaging is existential sequencing, not a nice-to-have. Own the spreadsheet before the first partner signs.

Saying no, on the record

“We don’t have to be their everything” dies quietly the tenth time bespoke money is offered. The scope-gravity operating rule is the constitutional defence, and only works if invoked.

Trust is the whole product

When strangers build on the API, tenancy isolation and the platform contract become the company’s reputation. One cross-tenant incident in year one costs more than every efficiency gain combined. That is why hardening is step 1, not step 5.

Three conditions
The compounding register

Six opportunities, O1 to O6

O1Objects × Workflows = Programs. Custom objects wired to workflow triggers become a no-code builder for the mentoring, awards and buddy schemes associations run in spreadsheets today.
O2The registry is a triple surface. Register an object once and get a REST endpoint, a widget and an AI-agent-callable MCP tool automatically.
O3Sync vs migrate. The native Events module (22 API routes) means events could be migrated in rather than built as the hardest Upbeat driver.
O4Generic driver to custom objects. A config-driven driver (endpoint, field map, target) turns future entity feeds from bespoke builds into configuration.
O5The commercial layer is unwritten. Metering is shipped but nothing prices it. Needed: a packaging one-pager, an agency ecosystem tier, the platform contract.
O6One WordPress build for every client type. A CRM-agnostic hub collapses the Upbeat and legacy Groundhogg product lines into one experience.
Compounding register O1 to O6
What “done” looks like
  • A client signs and receives a key, the portal, the docs, a Learn course and a certified partner directory.
  • Their agency builds whatever front-end they want, on whatever stack they want.
  • Their CRM, Upbeat, Groundhogg-migrated, native, or one day Salesforce, feeds the hub or is the hub.
  • We never see their website project. We meter their platform usage.
  • Every improvement we ship lands for every client simultaneously.

“Our team works on exactly one thing: the product.”

The end-state
The wider bets

Future horizons

Certification as trust

ISO 9001 and 27001 within 12 months, committed through the APNA contract. Certification becomes a trust asset and a partner asset: partners can certify through our quality management system.

New geographies

North America is a real goal, with Canada, Europe and South East Asia behind it. We expand by being the platform, with multi-currency and tax codes built in, not by opening a dev house in every country.

Partner economics

Train, certify and badge agencies through Agend Learn, then take a referral share. AI tools let them build front-ends on our MCPs and APIs while we own the data, security and workflows.

Resilience as advantage

Dynamics today is a single VPS, with no disaster recovery or failover. A true SaaS hub that keeps serving when Upbeat is offline turns their weakness into our differentiator.

The intelligence hub

A finance and insights layer above the ledger: reporting, a dynamic report builder, Orchestrate and, in time, chat with your data. Finance paired with what members actually do.

> 50%

of revenue is now licensing, for the first time ever. The revenue bridge is already crossing.

The wider bets
From the room, 8 July

FAQ  ·  cart, checkout and the suite

Q
Are we replacing WooCommerce, and WordPress?
WooCommerce goes for new builds: cart, checkout and subscriptions move onto our own gateway-agnostic engine. WordPress becomes one host among many, content plus our widgets, not the system.
Q
Where is product and pricing defined, centrally or per app?
Both. You set the event and ticket prices in Events, the course price in Learn. That flows to one central store where tax codes and membership pricing rules live and the sales manager sees everything.
Q
Can a member buy several things in one transaction?
Yes for the combinations that matter: membership plus event, the non-member to member upsell, company pays for all staff. Broad cross-bucket carts wait until the data says they matter.
Q
Do associations manage payments in Stripe?
No. Stripe and Xero are the ledger, not the interface. Agend sits above them, pairing finance with member activity: member versus non-member, ticket-to-membership upsells, what actually drives revenue.
Q
Do we build shipping?
No. Shipping is a 20-year headache we will not rebuild. Flat fee per country, or a Shopify integration for serious sellers. Physical goods sit on the storefront, separate from memberships, events and tickets.
Q
What happens if Upbeat or Dynamics goes down?
The site stays up. Reads serve from our hub, writes queue and retry until they land, and capacity rules live in our own store, so the member journey completes. When something is out of sync, it is visibly Upbeat, not the website.
Shopping cart / checkout meeting  ·  8 July 2026
From the room, 8 July

FAQ  ·  strategy and the transition

Q
Have we replicated Upbeat? Do clients still need it?
For most member-facing surfaces, technically no. Upbeat and Dynamics can stay as the top-tier system of record, or go offline entirely, and the site keeps working. That optionality is the wedge, not ripping Upbeat out.
Q
Who is to blame when the front-end breaks?
Today every outage lands on us, because we own the whole stack. Handing the front-end to the client's agency, with our APIs underneath, moves the line. The platform contract makes it explicit.
Q
How do the 16 bespoke Pro clients migrate?
Gradually, never big-bang. AMS clients first, because we control everything and there is less bespoke baggage. Each move is a staged project we run. Some bespoke features become the agency's job via APIs; a few are retired.
Q
What about new markets like North America?
Be the platform, not a dev house in every country. Multi-currency and tax codes are built into the product model. Agencies and partners build the front-ends; we supply the keys, widgets and rails.
Q
Are we getting certified?
Yes. ISO 9001 and 27001 within 12 months, committed through the APNA contract. It is a trust asset and a partner asset: partners can certify through our quality management system.
Q
Do we do hosting?
No. Hosting is all downside. Clients own their environment; we provide the platform, the plugins and the tools. Product, not projects.
Shopping cart / checkout meeting  ·  8 July 2026
docs/features/agend-platform-future/
← → or space  ·  F fullscreen  ·  P print