What makes a CRM a CRM for micro SaaS?

That the record fills itself from the product rather than from a salesperson. A micro SaaS has no sales team to keep a pipeline up to date, so the useful thing is a record per person that the website, the sign-in provider and the billing provider all write to, with a stage derived from what the person actually did. Deals and a sales pipeline are in Kicklace, off in a new workspace, and switched on under Settings → General when you want them.

How long does it take to connect?

One script tag in your site's head, and one address pasted into Stripe, is the usual first ten minutes. The tag starts recording visits immediately and Settings shows you the first one arriving; Stripe starts posting purchases as soon as its webhook is saved. Nothing has to be exported from another system first, because there is nothing to migrate for a product whose customers are already in its own tools.

Do I need to write any code?

Not for the website half: the tag is a copy and paste, and it hears your existing signup forms without you changing them. If you want events only your server knows about — a project created, a credit spent — the kicklace package on npm posts them in one line, and there is a plain HTTP endpoint if you would rather not add a dependency.

Can it email my customers?

Yes, to people who asked. Every email is tied to a list and to the exact wording that person agreed to, stored with the date and the address it came from, and every email carries a one-click unsubscribe. You can send a newsletter to a list, write to one person from their record, or let an automation send a welcome. There is no cold outreach and no way to import a purchased list.

What does it cost, and can I try it?

Nothing is charged yet: there is no card in Kicklace today. The planned plans are Founder at $9, Studio at $49 and Scale at $99 a month, priced by the number of people who sign in — people on record, workspaces and emails are not limited. Kicklace is invitation-only for now, and the waitlist is how you get in.

What happens to my data if I leave?

Everything held about one person — their fields, their identities, their subscriptions with the consent text, their whole timeline, the emails sent to them and the records merged into them — is one JSON file from that person's own page, and any view of any object exports as CSV. Deleting a person removes the record and everything that references it, and anonymous visitors are deleted on a schedule you set.

Kicklace, an AI-powered CRM for micro SaaS

CRM for micro SaaS

Why a CRM built for a sales team is the wrong shape for a one-person software company, and what Kicklace does instead: one script tag, one record per person, and follow-up that runs by itself.

Why Kicklace exists

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

A micro SaaS is a product run by one person or a few. By the time it has its first customers it already has four systems that each know part of the same human being: the website knows a browser that read the pricing page twice on a Tuesday, the sign-in provider knows an account with an email address, the billing provider knows a customer id and an amount, and the email tool knows a subscriber on a list. None of them knows those four are one person. Joining them up by hand is the job nobody has time for, so it does not get done, and the person who read the pricing page twice and never came back is never followed up.

A CRM built for a sales team asks a one-person company to be one. It wants a pipeline of deals, an owner on every record, stages somebody remembers to move, and a seat price that assumes a floor of people paying it. A micro SaaS has a signup form and a payment. What it needs is the record between them.

Kicklace is that record. One person, one row, from the first anonymous visit to the subscription and the renewal, with everything that happened to them on one timeline. Where they stand is worked out from what they did, never typed in by somebody, and the tools you already run are what fill it in.

How it differs from the CRM you have already looked at

There are two kinds, and Kicklace is neither of them.

A general-purpose CRM: A general-purpose CRM is a database you shape yourself: objects, fields and a pipeline, and then it waits for data. That is powerful, and it is a project — for a software product it means writing the integrations that fill it, and it means somebody moving stages by hand afterwards. Kicklace has the same model underneath, and you can add objects and fields of your own, but it arrives already knowing what a software company's customer does: a visit, a signup, a trial, a payment, a cancellation. The stages move themselves.
A sales-and-marketing platform: A platform in that category is built for reaching out: campaigns, sequences, lists you assemble. Kicklace is built for the people who came to you. It has no cold outreach in it and it is not an outreach tool: every email is tied to a list and to the words that person agreed to, and one click unsubscribes them. Its plans are priced by the number of people who sign in to Kicklace, and the number of people on record is not counted or limited, so a product with a lot of free visitors is not paying for the visitors.
What that leaves out: There is no lead scoring, no sequence builder, no dialer and no purchased-list import. A stage cannot be dragged into place by hand on the lifecycle either — it is derived, and that is the point of it.

Side by side with the products people name in the same sentence: what Kicklace is.

How the tag works

One script tag is the whole of the website half.

Script tag · sample key

<script
  async
  src="https://www.kicklace.com/api/in/wk_sample/track.js">
</script>

Or one line in your server: the kicklace package on npm posts the same events from code, with a secret key. The package.

One script tag, once, just before the closing head tag on every page. It keeps one random id in the browser's own storage — no cookies — and posts a page read, the campaign and referrer the visitor arrived on, and anything you have marked as an event. A visit from an automated browser sends nothing at all.

The same tag hears your signup forms without touching them. It listens for a submit, reads the email box and the name box, and never calls preventDefault, adds markup or changes an id: your form's own handler and its own success message are exactly what they were. A form marked with the list it belongs to is a signup; so is every form with an email box, if you switch that on. The words the person agreed to come from the form — the attribute you set, or the label of the required tick box they ticked — and where there are none, the person is recorded with their address and put on no list, because a signup with no consent behind it is not permission to email anybody.

The key in that address is a public key: it is in the page, it is meant to be, and it only works from the website addresses your workspace allows. Your secret keys never appear in a browser.

How identity resolution works

One person, one record, across devices and across the tools that see them.

The hard part of a customer record is not storing it. It is that the same person arrives as a browser on Monday, an email address on Wednesday and a Stripe customer id on Friday, from two devices, and has to come out as one row.

Email is the durable key. A known email arriving with a browser id Kicklace has not seen attaches that browser to that person. A known email arriving with a browser id that belongs to a different, still-anonymous person merges that person in: identities, timeline, subscriptions and links are all repointed, the fields are unioned, and the earliest first touch wins — so the campaign that first brought them in survives the merge and is still there a year later. Two people who both have email addresses are never merged automatically; that one is offered to you on the record, with a preview of what would move.

Beyond the email address and the browser id, a person can be found by an account id, an install id, a Stripe customer, a Clerk or Kinde user, or a GitHub login. That is how a subscription event carrying no email address at all still lands on the right record: the Stripe customer id was written down the first time an event arrived carrying both.

The customer timeline

Everything that happened to one person, in one place, with who did it.

Fields

Click a value to change it.

Name: Ada Marsh
Email: ada@northwindprint.example
Phone: +1 208 555 0143
Title: Owner
OS: mac

Identities

email: ada@northwindprint.example
anon: mtol9kx4jjq5co1a
account: acct_5f2a91

First touch never changes, even after a merge: google · cpc → /pricing.

Timeline

Everything that happened, and who did it. Current stage: Purchaser.

Today

Purchase
Purchased credits
from google · cpc · /pricing
7:49 PM
Stage
Moved to Purchaser
Lifecycle events (purchase)
7:48 PM · automation

Yesterday

Email out
Sent: Your first project, step by step
to ada@northwindprint.example · Product updates
7:49 PM · Sent

Sun, Sep 6

Note
Called back about the seat count; wants three
9:49 PM · Ben Okafor

Thu, Sep 3

Account
Created an account
from google · cpc · /pricing
9:49 PM
Form
Subscribed to Product updates
“Send me product updates.” · 203.0.113.9
8:49 PM
Visit
Pageview /pricing
from google · cpc
7:49 PM

Connections

Tasks

What to do next, who it is for, and when it is due.

Send the three-seat quotedue Fri · Ben Okafor
Call back about seatsdone 3 days ago by Ben Okafor

Sample data, not a customer's. The timeline, the fields and the identities are drawn by the record page's own components.

The lifecycle, worked out for you

Six stages a new workspace starts with, and nobody moves anybody by hand.

1
Visitor
Seen on the website
2
Subscriber
Gave an email address
3
Account
Created an account
4
Activated
Did the first real thing in the product
5
Purchaser
First purchase
6
Repeat
Bought again

A stage comes from an event. A page read makes a Visitor, a signup form makes a Subscriber, an account makes an Account, a paid invoice makes a Purchaser, a second one makes Repeat. Two more — Trial and Churned — are switched on by a workspace that has a trial or a subscription, and are not there by default, because a product with neither should not carry two empty columns for ever.

The lifecycle in full, and every event and what it moves.

What follow-up looks like

Written in plain English, shown as rules you can read, and off until you turn it on.

Welcome to Product updates

A sample automation.

When

Someone joins Product updateslistProduct updates

Wait

No wait; it runs straight away.

Only if

Subscribed to Product updateslistProduct updates

Has not had this email before

Then

Send Welcome to Product updatestemplateWelcome to Product updateslistProduct updates

runs aloneIt is on, and it emails people without asking again.

You describe what should happen and Kicklace turns it into four blocks over your own stages, lists and templates: when, wait, only if, then. You can write one by hand instead, and you can replay it against the last seven or thirty days to see what it would have done, without sending anything.

A send always names a list and always checks the subscription again at the moment it runs, so somebody who left the list between the trigger and the send is not emailed. An email caused by what the person just did — a receipt, a password, a reply — needs no list, but it does need them to have done something: bought, signed up, subscribed, been activated, or written to you.

Every card ends with how much that one is trusted with — drafts only, proposes and you approve, or runs alone. It is granted an automation at a time, not once for the whole product.

The automation language, and what automations do.

What it costs

Three planned plans, priced by the people who sign in.

Founder · $9 a month: For solo founders with their first customers. One person, unlimited workspaces, and no limit on people on record or emails sent.
Studio · $49 a month: For small teams, or one product with a lot of leads. 5 people, then $9 each a month, unlimited workspaces, and no limit on people on record or emails sent.
Scale · $99 a month: For products with tens of thousands of users. 15 people, then $6 each a month, unlimited workspaces, and no limit on people on record or emails sent.

Nothing is charged yet. There is no card in Kicklace and no invoice; these are the planned prices, and the waitlist asks which one you would want. Pricing.

Questions

What makes a CRM a CRM for micro SaaS?: That the record fills itself from the product rather than from a salesperson. A micro SaaS has no sales team to keep a pipeline up to date, so the useful thing is a record per person that the website, the sign-in provider and the billing provider all write to, with a stage derived from what the person actually did. Deals and a sales pipeline are in Kicklace, off in a new workspace, and switched on under Settings → General when you want them.
How long does it take to connect?: One script tag in your site's head, and one address pasted into Stripe, is the usual first ten minutes. The tag starts recording visits immediately and Settings shows you the first one arriving; Stripe starts posting purchases as soon as its webhook is saved. Nothing has to be exported from another system first, because there is nothing to migrate for a product whose customers are already in its own tools.
Do I need to write any code?: Not for the website half: the tag is a copy and paste, and it hears your existing signup forms without you changing them. If you want events only your server knows about — a project created, a credit spent — the kicklace package on npm posts them in one line, and there is a plain HTTP endpoint if you would rather not add a dependency.
Can it email my customers?: Yes, to people who asked. Every email is tied to a list and to the exact wording that person agreed to, stored with the date and the address it came from, and every email carries a one-click unsubscribe. You can send a newsletter to a list, write to one person from their record, or let an automation send a welcome. There is no cold outreach and no way to import a purchased list.
What does it cost, and can I try it?: Nothing is charged yet: there is no card in Kicklace today. The planned plans are Founder at $9, Studio at $49 and Scale at $99 a month, priced by the number of people who sign in — people on record, workspaces and emails are not limited. Kicklace is invitation-only for now, and the waitlist is how you get in.
What happens to my data if I leave?: Everything held about one person — their fields, their identities, their subscriptions with the consent text, their whole timeline, the emails sent to them and the records merged into them — is one JSON file from that person's own page, and any view of any object exports as CSV. Deleting a person removes the record and everything that references it, and anonymous visitors are deleted on a schedule you set.

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.