Product

CRM that does not stop at the sale

The CRM in Stackap Business holds clients, leads, deals, quotes and tasks, and links each one to the bookings, payments and books that follow.

What it does

A client record carries several phones and emails, several properties, a feedback history and merge-safe identity: duplicates are detected on a schedule and merged atomically, so two records for one household become one without losing bookings. Leads are captured from forms, a web chat widget, tracked clicks and inbound calls, with attribution recorded so you can see which source produced a customer.

Deals move through pipeline stages in a single database transaction, with an activity trail for each move. Quotes are first-class: a quote has a lifecycle, a public link the customer opens, an optional budget for costing the job, and can become a booking or a job. Teams also get task boards with columns and groups for the internal work around customers.

Referral and partner programs are part of the same model. Referrers and sales partners have their own portal sign-in, and commissions are calculated and tracked against the sales they produce.

How it works

Where this stands

Stackap Business is working software for running a service business, with its capabilities documented from the code. It is being brought onto the Stackap platform, so an outside agent can operate it with the same scoped tokens, approvals and API that Stackap Cloud uses. That work is in progress. The CRM can be used inside the business software now; it is not yet exposed through the Stackap API for an outside agent.

The point of putting this beside finance and scheduling is that a customer's record is not a dead end. From a client you can reach every booking, the invoices and payments against them, the messages exchanged and the review they left. Searching "who has not paid" and "who has not booked in 90 days" are questions about the same customer, answered from the same place.

Early-access scope

There is no separate "company" or "account" object for customers. A commercial customer with several sites is modeled as one client with several properties.
There is no explicit lead-score model. Conversations are scored, and conversions can be flagged by hand, but a numeric score on every lead is not built.
There is no segment builder or journey designer. Campaigns target a fixed set of audiences such as all clients or recurring clients.
Customer data currently lives in more than one place inside the software; consolidating it into a single customer graph is planned work.

Questions

Can I import my existing contacts?

Import tooling exists inside the software, but a supported import path for outside teams is part of early access and not yet documented. Ask before assuming.

Is this a sales CRM or a service-business CRM?

It was built for service businesses, where a sale becomes a scheduled job. The sales page covers pipelines and quotes. Teams that sell without scheduling work may find parts of it unneeded.

Stackap is in early access. Tell us what you run and we will reply with a straight answer about whether it fits.

Ask for an invitation

Last updated 2026-10-03.