Website builders, CRMs, booking tools, and payment processors are commodity goods in 2026 — cheap, abundant, largely undifferentiated. What a local business cannot buy off the shelf is a reliable stream of nearby customers who already trust them. They rent that stream from Google, Meta, and the marketplaces, at rising cost, and it stops the moment they stop paying.

The HomeTown Commerce Ecosystem rests on a single bet: if you own community-level discovery, you can attach the commerce stack to it at low acquisition cost and high retention.

Merchants retain ownership of their customers, site, data, and payment relationship. That is a deliberate constraint, not a marketing line — Section 05 explains why it is also a defensible commercial position rather than a concession.

For the merchant

• Acquisition cost has risen faster than local margins, and paid channels reset to zero the day the budget stops.
• The average local business runs four to seven disconnected tools that do not share data, so nothing compounds.
• Marketplaces that do deliver demand take ownership of the customer relationship, leaving merchants renting access to their own buyers.

For the community

• Local discovery has fragmented across platforms optimized for national advertisers rather than for a specific neighbourhood.
• Consumers say they want to buy local, then default to whatever ranks first. Intent exists; the surface to act on it does not.

For our partners

• Consultants, agencies, and chambers already hold the trust relationship with local merchants. They lack a product that captures recurring value rather than one-time project fees.

3.1  HomeTown.Social — Demand

Role: generate qualified local demand and route it to merchants, through the community feed, daily news edition, events, marketplace, business directory, groups, neighbourhood feeds, and member profiles.

Not in scope: payment processing, storefront hosting, order management. HTS hands off; it does not transact.

Success is measured by qualified referrals delivered per merchant per month. Not members, not posts, not listings — referrals. Every other number on the platform is a leading indicator of that one.

3.2  TownCore™ — Operations

Role: the system a merchant runs their business on once demand arrives. White-labeled GoHighLevel, integrated with AMP Pay, presented entirely as HomeTown. The merchant never interacts with the underlying platform.

Capabilities: sites and landing pages, online stores, appointment booking, CRM, email and SMS, automation, AI content, funnels, forms, reputation management, subscriptions, analytics, dashboards.

Stated plainly: building on GoHighLevel is right for speed and capital efficiency, and it creates real dependency. Margin, roadmap, and continuity sit partly with a third party. That is a managed risk, not an absent one, and it should be disclosed to investors rather than discovered by them.

3.3  AMP Pay — Transactions

Role: process payments and monetize the volume the ecosystem creates. Funds move from customer to merchant; neither HTS nor TownCore takes possession of merchant funds.

3.4  WRN — Distribution

Role: acquire merchants through trusted intermediaries rather than direct sales headcount.

Why this matters more than it appears: WRN is not a channel program bolted on the side. It is what makes the unit economics work. Direct sales to local merchants at SMB price points does not pay for itself; a $150-per-month subscription cannot carry a $1,200 fully loaded acquisition cost on a 24-month payback. Partner-led acquisition converts a fixed sales cost into a variable revenue share — the difference between a model that scales and one that does not.

1. Resident opens the daily edition on HomeTown.Social
2. Discovers a business through the feed, directory, or an event
3. Visits that merchant's Business Home
4. Converts on the merchant's TownCore site or store
5. Pays through AMP Pay
6. Merchant receives funds; transaction data enriches the CRM
7. Better data improves targeting, ranking, and repeat purchase
8. Merchant success becomes proof for the WRN partner
9. Partner introduces more merchants; local supply deepens
10. More reason for residents to return — and the loop tightens

Each pass should lower blended acquisition cost and raise retention. If it does not, the ecosystem thesis is wrong and this is four mediocre point solutions in a trench coat. That is the falsifiable claim at the centre of the business, and Delta is where it gets tested.

What we are not

We are not building a better Shopify. Storefront software is not scarce.

What we are

The commerce operating system for a place. Every merchant gets a way to be found, to tell their story, to sell, to communicate, and to grow — connected, in one system. Open · Q13

The merchant-ownership position

Merchants own their customers, site, data, and payment relationship. Competing marketplaces do the opposite, and merchants have learned what that costs.

This is not charity and should not be pitched as such. It is a commercial trade: we give up the ability to disintermediate our merchants, and in exchange we get a lower-friction sale, better retention, and a credible reason for chambers and economic development organizations to endorse us — a channel closed to marketplace-model competitors by construction. Ownership is our moat with the channel, not a favour to the merchant.

The integration argument, made properly

Version 1.0 conceded that no single component is revolutionary. True, and conceded too quickly. The defensible form: a merchant running five vendors has five bills, five logins, five support paths, and zero data flowing between them. Their marketing does not know what their POS knows. Consolidation is worth real money, and every additional surface they run on us raises switching cost and improves the data that makes the next surface work better. The integration is the product. The components are inputs.

Actual competitive set

Version 1.0 benchmarked against Shopify, Meta, and Google. Those are not who we lose Delta merchants to.

Note rows four and six. Any GoHighLevel agency can replicate the TownCore stack in a weekend, and any community Facebook group already owns the attention we are competing for. HomeTown.Social and WRN are the defensible assets; TownCore and AMP Pay are the monetization. Resource accordingly.

The ecosystem is coherent at steady state and inert at zero. HTS delivers no referrals without merchants and residents; TownCore is a commodity CRM without HTS referrals; WRN partners will not stake client relationships on an unproven product.

Delta is already the answer to "which town first." The remaining question is what has to be true there before a second market opens.

Two structural questions

1. Is the unit of expansion the community or the partner? Geography-first builds density and network effects but scales slowly. Partner-first scales quickly and risks thin coverage everywhere and defensibility nowhere. These need different products, comp plans, and capital. The plan currently implies both. Open · Q5
2. What is the minimum merchant and member density at which HTS becomes useful? Below that threshold, referral volume is not low — it is zero, and every paying merchant churns. Estimate it before launch, not after. Open · Q16

This section is new, and it exists because reviewing the live platform changed my assessment of what the binding constraint actually is. It is not strategy. It is infrastructure.

HomeTown.Social currently runs on a combination of Ghost, JSONBin, browser localStorage, and a partial Supabase migration. That stack is a reasonable way to get a community platform in front of real residents quickly, and it has clearly worked — the product is live, feature-rich, and further along than most pre-seed platforms. The concern is not what it took to get here. It is what it cannot carry next.

Three constraints that block the commerce layer

• Data durability. A system where records can exist only in one browser's cache, where saves can fail silently when storage fills, and where recovery requires a person to open the right device and push data up, is not a system merchants can run a business on. The moment a merchant's customer list lives there, an ordinary browser cache clear becomes a business-ending event for them and a liability for us.
• Authentication. Four-digit PINs held client-side are appropriate for a neighbourhood feed. They are not appropriate for an account that will hold customer records, and they are nowhere near what a payment integration will require. This has to change before AMP Pay touches anything, and changing it later means migrating every member account that exists by then.
• Shared-tier storage limits. Payload ceilings that require periodic image cleanup are workable for a single community. They do not survive five communities, and they will not survive merchant media.

What this means strategically

The commerce ecosystem described in this document cannot be layered onto the current data foundation. The migration to a durable backend is not a technical chore to schedule alongside growth — it is a precondition for the revenue model, and it is the most urgent item on the roadmap. The Cloudflare direction already named in the platform roadmap is a sound destination; what matters is sequencing it before merchant and payment data arrives rather than after.

There is a real opportunity cost argument for moving now: every member, listing, and referral record created before the migration is a record that has to be moved, reconciled, and verified later.

Smaller items worth a pass

• Public social links in the site footer still point to the Ghost theme's own accounts rather than HomeTown.Social's.
• The default Ghost publication cover is serving as the Open Graph image, so shared links do not carry the brand.
• Public member, post, and business counters currently display zero to signed-out visitors. On a community platform, visible emptiness is a conversion problem — consider showing them only past a threshold.

Revenue by entity

HomeTown.Social — sponsorship of the daily edition, featured listings, sponsored content, premium placement, community sponsorships, membership upgrades. The sponsorship inventory is already built into the product. Realistically modest early: this platform's job is to lower TownCore's acquisition cost, and it should be resourced as demand generation rather than held to a near-term revenue target.

TownCore — recurring subscription across Starter, Growth, Professional, Enterprise, plus setup, store build, AI services, marketing packages, implementation, training, support. Four tiers are named with no prices, which is the first thing any reader looks for. Open · Q2

AMP Pay — processing spread, transaction revenue, subscription billing. Take rate depends entirely on the structure question in 3.3.

WRN — a cost line before a revenue line. Commissions and residuals reduce contribution margin; enterprise partnerships may offset. Model it as acquisition cost.

What must be established

Two of these govern everything else: gross margin after platform costs and payback period. If GoHighLevel wholesale plus support plus partner commission consumes most of the subscription price, the software line is an acquisition vehicle for payments rather than a business — and the plan should be rebuilt around payments economics deliberately rather than by accident.

The last row is new, and it is not a small one. Daily local editorial is the demand engine, which makes it a recurring per-market cost that must appear in the launch model for every community, not just Delta.

• The four-entity separation is clean and the boundaries are correctly drawn.
• Merchant ownership of customers, data, site, and gateway is a real differentiator with a real channel benefit.
• Partner-led acquisition is the correct structural answer to SMB acquisition cost — and the referral infrastructure to support it is already built.
• The flywheel logic is sound, and the daily edition solves the habit problem that usually kills local platforms.
• Separating communities (places) from groups (interests) is a genuinely good product decision and a real differentiator against Facebook.
• "Operating system for community-powered commerce" is a position no incumbent occupies end to end.

Down from 30 in the first draft — the live platform answered eight of them. The first six change the shape of the document; the rest fill it in.