Platform
Composition, not codegen.
An AI can write you a storefront in an afternoon. What it cannot give you is a backend, an admin, a mobile app and an upgrade path that all agree with each other. Kikstart composes those from modules that are written once and maintained for everyone.
Three layers
Solution, module, domain.
What you buy: a named bundle of modules for a kind of business. Commerce, Field, Productivity.
What can be switched on: one admin area with its tables, screens, settings and assistant tools. Products, Orders, Employees, Visits.
How modules group for a person reading the list: commerce, people, performance, operations, field, configuration, oversight.
What you get
The parts an app builder leaves out.
Grids, forms and filters authored per module, with the columns and defaults set for you. Not a generic dashboard with your logo on it.
One Postgres database per customer, with row-level security for every role inside it. Analytics rollups, audit trail and file library included.
Create, configure and operate by chat. The assistant writes configuration the modules validate and acts through the same permissions as the person asking; it never writes code into your app.
The storefront module reads from Kikstart's own catalog or from your Shopify store through one contract. Swap the backend; keep the app.
Expo and React Native, sharing the data layer, types and design tokens with the web. Offline read cache and a durable write queue for the field.
A fix to a module reaches every app built on it. Schema changes replay to every customer database in order, with a ledger of what ran where.
AI
Where the AI actually is.
Three assistants, one contract. The console assistant creates and provisions. The admin assistant operates a store or a team. The customer-facing assistant answers shoppers. All three act through module tools, never raw SQL, never raw code.
Creates your store from a description, provisions your database and shapes the first version of the site.
Operates your business: catalog, orders, copy, sections, rosters, targets. Each module ships the tools it may use.
Answers shoppers and field agents inside the app, with the same row-level security as a signed-in user.
A module declares what an assistant may do with it. The catalog of tools is seeded, checked and versioned with the module.
Cross-conversation memory that the owner can read and retract, entry by entry.
llms.txt on the site and the docs, so any assistant can cite the published text rather than a stale summary.
Under the hood
Boring where it should be.
Next.js on Vercel, Postgres on Neon, Expo for mobile, PayFast and Stripe for payments. Nothing exotic; nothing you cannot hire for.
See it with your own catalog.
Apply for console access to create a store on your subdomain and bring your products across from WooCommerce or Shopify, or talk to us about a custom build.