What is a customer platform, as opposed to a CRM?

A CRM is where customer records live. A customer platform is that plus the things you do with them: the lists and the sending, the follow-up that runs by itself, the charts, and the doors that fill the records in. The practical difference is that they are the same data, so an email knows which person it went to and an automation reads the same stage a chart counts.

Will it replace my email tool?

For lists, templates, newsletters, one-to-one email and your own sending domain, yes — including bounce and complaint handling and a preferences page where somebody can see every list they are on. What it will not do is cold outreach: every send is tied to a list and to the words that person agreed to, and there is no way to import a purchased list.

Does it replace Stripe?

No. Stripe charges the money and remains the source of truth about it. Kicklace takes Stripe's webhook directly, with no code of yours in between, and turns a payment, a refund, a trial, a renewal or a cancellation into a stage and a row on the person's timeline.

Do I still need product analytics?

If you want to know which screen in your product is used, yes. Kicklace records what one person did and counts those events across people, which answers where customers come from and what happens to them; it has no session recordings and no in-app funnels, and it is not built for millions of events a day.

How much of it can the AI run?

The setting up, most of the asking, and the drafting. Claude connected to your workspace, or Ask Kicklace inside the app, can make lists, write templates, add stages and fields, build views and charts, add notes and tasks, and draft an automation for you to read. It never sends an email and never deletes anything: those become one-sentence proposals on an Approvals screen where a person decides.

Kicklace, an AI-powered CRM for micro SaaS

AI customer platform

The record, the email, the automations and the AI as one thing rather than four subscriptions — what that takes off a small company's list, and the four tools it does not replace.

One thing, not four

Kicklace is an AI-powered CRM and customer platform for micro SaaS companies.

A customer platform, rather than a CRM with an email tool bolted to it, means the record and the sending and the follow-up and the model are one thing: the email knows which list it belongs to and which person it went to, the automation reads the same stage the chart counts, and the paragraph at the top of a record is written from the same timeline the board is drawn from. Nothing has to be kept in step, because there is only one of everything.

For a company of one or three, that is not an architectural preference. It is the difference between four subscriptions with four exports and a Zapier bill between them, and one place where a person exists once.

The four parts

Each is ordinary on its own. Being the same data is what makes it worth having.

The record: One row per person, from the first anonymous visit to the subscription, filled by a script tag on your site and by the tools you already run. Organizations, deals if you want them, and objects of your own beside it. Where each person stands in the lifecycle is worked out from what they did.
The email: Lists with the consent behind them, templates, newsletters to a list, and one-to-one email from a person's record — with your own sending domain, one-click unsubscribe, and a page where somebody can see every list they are on. Replies land back on the record, and the emails you send from your own mailbox can land there too.
The automations: When, wait, only if, then — written in plain English, shown as rules you can read, replayed against the last month before you arm them. They send, notify, move a stage, set a field, write a task, post to your Slack channel, or make a signed request to your own server.
The AI: Set the workspace up by asking, get a chart from a question, have an automation written for you, read one paragraph and a next step at the top of every record. On by default and off with one switch under Settings → General, metered against your plan, and never able to send or delete without a person deciding.

Everyone, in one place

People, organizations, deals and objects of your own, with saved views over them.

Person	Stage	Lists	First seen	Last activity
AMAda Marshada@northwindprint.example	Purchaser	Product updates	google · cpc → /pricing	2 h ago
BOBen Okaforben@harborlights.example	Activated	Product updates, Tips	reddit · social → /signup	yesterday
CVCleo Vargacleo@tessellate.example	Account	none	direct → /	3 days ago
DADev Ananddev@copperline.example	Subscriber	Product updates	newsletter → /product	5 days ago
·Anonymous 7f3a2cno email yet	Visitor	none	chatgpt.com → /how	just now

Sample data, not a customer's. Tick a few rows to see what a selection can do.

What it takes off the list

Five things a small software company usually runs separately.

A CRM: The obvious one, but the useful half is small: contacts, companies, a timeline, notes, tasks, saved views, import and export, and a board when you want one. What it does not carry over is the sales apparatus — owners on every record, forecast fields, stages somebody keeps up to date — and deals are off in a new workspace until you switch them on.
An email tool: Lists, templates, broadcasts, scheduling, your own sending domain, bounce and complaint handling, and a preferences page. The difference is that the list is not a copy of your customer data that goes stale: it is the same record, so “everyone who signed up this month and has not been activated” is a view rather than an export.
The spreadsheet: The one with the tab of people who emailed you, the tab of who has paid, and the column somebody stopped filling in. It is the honest one to name, because for most micro SaaS companies that is the thing actually in use, and the reason it fails is not discipline: it cannot join a browser to an email address to a payment, and it cannot send anything three days later.
The webhook forwarder: The small service in the middle that catches Stripe and posts it somewhere. Kicklace takes Stripe, Clerk, Kinde, Vercel and GitHub directly, with a signature check and an address you paste, so there is no function of your own to keep alive; and it sends its own outgoing webhooks, signed and retried, when you want the traffic to keep going.
The dashboard you were going to build: Charts asked for in plain English or built by hand, over your own stages, lists and fields: counts, funnels, groups, cohorts by the week people arrived, conversion over time, which sources end well, and who came back. Arranged on a grid you drag, on as many dashboards as you want.

And what it does not replace

Four you should go on paying for, said here rather than found out later.

Product analytics: Kicklace records what a person did, one person at a time, and it counts those events. It is not a product analytics tool: there are no session recordings, no funnels through your app's own screens, and no event volume built for millions of rows a day. If you want to know which button in your product is used, that is a different tool and it should stay.
A support desk: Email arrives on the record and you can answer from it, and a support inbox on your own domain forwards to wherever you read mail. That is a small company's inbox, not a ticketing system: no queues, no SLAs, no shared assignment, no macros. A team that needs those needs a help desk.
Billing itself: Stripe charges the money and stays the source of truth about it. Kicklace reads what happened — a payment, a refund, a trial, a renewal, a cancellation — and turns it into a stage and a timeline. It does not hold cards, issue invoices or run a subscription.
Your sign-in: Clerk, Kinde or whatever you use goes on being your authentication. Kicklace listens for the sign-ups and sign-ins and keeps one person per human across both, and there is nothing to migrate.

Nothing is charged for Kicklace yet, and the planned plans are on Pricing. What the AI half really does: AI CRM for micro SaaS. Why it exists at all: CRM for micro SaaS.

Questions

What is a customer platform, as opposed to a CRM?: A CRM is where customer records live. A customer platform is that plus the things you do with them: the lists and the sending, the follow-up that runs by itself, the charts, and the doors that fill the records in. The practical difference is that they are the same data, so an email knows which person it went to and an automation reads the same stage a chart counts.
Will it replace my email tool?: For lists, templates, newsletters, one-to-one email and your own sending domain, yes — including bounce and complaint handling and a preferences page where somebody can see every list they are on. What it will not do is cold outreach: every send is tied to a list and to the words that person agreed to, and there is no way to import a purchased list.
Does it replace Stripe?: No. Stripe charges the money and remains the source of truth about it. Kicklace takes Stripe's webhook directly, with no code of yours in between, and turns a payment, a refund, a trial, a renewal or a cancellation into a stage and a row on the person's timeline.
Do I still need product analytics?: If you want to know which screen in your product is used, yes. Kicklace records what one person did and counts those events across people, which answers where customers come from and what happens to them; it has no session recordings and no in-app funnels, and it is not built for millions of events a day.
How much of it can the AI run?: The setting up, most of the asking, and the drafting. Claude connected to your workspace, or Ask Kicklace inside the app, can make lists, write templates, add stages and fields, build views and charts, add notes and tasks, and draft an automation for you to read. It never sends an email and never deletes anything: those become one-sentence proposals on an Approvals screen where a person decides.

Join the waitlist

We are onboarding one company at a time. Leave your email and we will let you know when your workspace is ready.