Skip to main content

What is Kvick?

Kvick is a machine that builds bespoke commercial systems. Operated by 1536849 B.C. LTD., founded by Thomas Butler Anderson, Campbell River, BC. The first thing the machine built — the Hub — is a holistic commercial retail system, and the bike-shop industry is the first vertical it was shaped for. Everything built for that vertical is meant to be reused, recycled, and reinvented for the next one.

The anatomy the machine produces is a Bespoke Web System (BWS): one Cloudflare Worker, one D1 database, one R2 bucket — single-tenant per customer — exposing two surfaces (the operator-facing Hub + the public-facing website), both fed by the same store.

Drafted from planning · v0.1

The product family

The Hub is Kvick's platform pattern, applied across verticals. Each vertical is its own single-tenant deployment per customer. Verticals live and ship on their own schedules; the Hub's cross-vertical primitives (helm-editable, audit chain, AI Support, Substrate Line) are shared infrastructure.

Verticals shipping or in progress

VerticalBrandPriceStatus
Bike shopsKVICK.BIKE$199/month flatLive — Swicked Cycles is the first instance. The subject of this bible. See What is the Hub?.
AccountingTBDTBDPlanned (Scenario 3 candidate — see Three Scenarios)
Motorcycle shopsTBDTBDPlanned (Scenario 2 candidate — most patterns port from bike)
Future verticals (marketplaces, specialty service businesses, plumbers, electricians, HVAC)TBDTBDRoadmap, via the BWS machine and the Three Scenarios

Each vertical's bible documents its own slice surface (Sales / Service / Customers / Inventory variants per industry). The bike-shop vertical exercises every Hub primitive, so this bible is also the de-facto reference for the platform-level mechanics.

Discontinued: the "$29 tradesperson" static-site product

An earlier product line — individual-tradesperson static lead-generation websites at a $29/month price point — was discontinued. KVICK has moved past it. The doctrine that survived was cross-instance pattern detection: when many instances in a vertical begin showing the same new need, the signal feeds the vertical's L2 canon (see Process Library). That mechanism applies to every vertical the BWS machine produces.

Why a vertical strategy at all

A generalist POS amortizes engineering across many industries but can't be excellent at any one of them. The Hub takes the opposite bet: build the platform primitives once (single-tenant per customer, helm-editable in-situ edit, audit chain, AI Support, Substrate Line), then build the vertical specifics once per industry. The vertical specifics — what an "inventory line" means for a bike shop vs. a CPA vs. a motorcycle dealer — are where the operator's daily work lives.

Bike shops are the wedge because the market is well-defined, the incumbents (AIM, Lightspeed) have visible weaknesses, and the BC mountain-bike community is a high-trust referral network. Accountants are the second wedge for similar reasons in a different shape. Motorcycle shops are next because the workflows look more like bikes than accounting, so most of the bike-shop vertical's primitives port directly.

Same platform, divergent verticals

The Hub's promise to every customer in every vertical is the same:

  • Single-tenant per customer. Your shop's data is yours; your deployment is yours.
  • In-situ editing (the helm-editable chassis). Adapt the system to the way you actually work, without filing tickets.
  • Tamper-evident audit chain. Every change is hash-chained, every event stamped with the build version that was running.
  • AI Support. The bubble reads your shop's bible, your schema, your operator history.
  • The Substrate Line. Some things are platform-level and stay that way across verticals; some things are per-vertical; some things are per-shop. The line is explicit.

Branding

  • Kvick — the company. Two-tone navy + blue. The K logo (the chevron) is the universal mark.
  • KVICK.BIKE — the bike-shop vertical brand. Add orange (#c8410c) as the accent for in-shop affordances.
  • Each shop deployment of the Hub gets that shop's branding on the customer-facing surfaces (receipts, public site, SMS sender), but the operator-facing app keeps Kvick's voice.

Why "Kvick"?

Swedish for "quick." Short, ownable as a domain (.ca, .bike), pronounceable everywhere. The naming pattern is: parent Kvick + period + vertical (Bike, future verticals likely Trades, Auto, etc. as separate brand TLDs).

See also

  • What is the Hub? — the product this bible covers
  • Business model — pricing, unit economics for both tiers
  • Customer & market — the Hub's target market