A recent roundup walks through SaaS startups worth watching in 2023, with deep dives on Attentive, Instabase, and Tessian. The names matter less than what their feature lists reveal about how software is being bought and built right now.
Worth reading for the pattern, not the product placements.
- Attentive focuses on personalised SMS messaging tied to e-commerce behaviour.
- Instabase automates document and workflow processes with machine learning.
- Tessian uses machine learning to catch email threats that rules miss.
- All three sit at the intersection of data, automation, and integration.
- All three pitch outcomes to specific buyer roles, not generic features.
What the three have in common
Strip away the verticals and the three startups are doing the same thing in different costumes. They take categories that used to be rules-based — messaging, document processing, email security — and rebuild them on top of machine learning trained on customer data. They integrate into the systems their buyers already use, and they charge on outcomes their buyers can measure.
That's the SaaS playbook of the last few years, working as intended.
Our analysis
For anyone running a software selection process, the pattern matters more than the names. Three things to notice.
Integration is the product, not a feature.** None of these tools positions itself as a destination. They position themselves as a layer that sits inside Salesforce, Slack, Shopify, or your email client. This isn't accidental. The integration is how they get data, how they stay embedded, and how they make switching painful. If a SaaS pitch doesn't lead with integration, ask why.
The buyer pitch has a name and a title.** Attentive sells to e-commerce growth teams. Instabase sells to operations leaders drowning in unstructured documents. Tessian sells to security teams that already know their email gateway is leaking. Specificity signals that the vendor understands the workflow. Generic pitches signal a feature looking for a home.
The data flywheel compounds in one direction.** More usage produces better models, which produces stickier products, which produces more usage. This is healthy for vendors and worth understanding honestly on the buyer side. You're not just buying software — you're feeding a system that gets harder to extract from over time.
The consolidation watch: a wave of these tools will get acquired or merged. The survivors will be the ones that turned their data advantage into a visible outcome their customers can point to in a board meeting.
Who should care
| Role | What to watch for |
|---|---|
| Software buyers | Does the pitch name your workflow, your title, and your current stack within the first ten minutes? If not, it's a feature, not a product. |
| Product managers | How does this tool get its training data? The answer tells you whether the moat is real or decorative. |
| Operations leads | Is the integration two-way? Tools that only read from your systems are features. Tools that write back and automate across them are products. |
| Finance and procurement | The data flywheel creates switching costs that weren't in the contract. Model the exit cost before you sign. |
What to watch next
Watch for SaaS pitches that lead with "we use AI" and trail off. The interesting ones lead with a specific workflow, a specific buyer, and a data advantage you can see working in the demo. If you can't name all three in the first ten minutes, you're looking at a feature.
Bottom line: in 2023 SaaS, the integration story is the product, the buyer is specific, and the data flywheel is the moat. Pick vendors accordingly.
Key takeaways
- Integration depth is the strongest signal of a real SaaS product, not a feature.
- Specificity in the buyer pitch usually beats generic AI language.
- Data flywheels drive switching costs — model the exit cost before you sign.
- The vendors that survive consolidation will turn their data advantage into a visible customer outcome.
Frequently asked questions
What do Attentive, Instabase, and Tessian have in common?
They all rebuild rules-based categories on top of machine learning, integrate into the systems their buyers already use, and pitch to specific buyer roles rather than generic companies.
What does a strong SaaS integration story look like?
It shows the tool living inside the systems the buyer already runs — CRM, email, ticketing, document store — rather than positioning itself as a separate destination.
Why is specificity in the buyer pitch a good sign?
It usually means the vendor has worked hard to understand a real workflow, which is a much better signal than a generic "AI-powered" claim.
What's a data flywheel and why does it matter?
A data flywheel is the loop where more usage produces better models, which makes the product harder to leave. It drives switching costs and is worth pricing in on both sides of the deal.
How do you spot a SaaS feature disguised as a product?
If the pitch can't name a specific workflow, a specific buyer, and a specific data advantage in the first ten minutes, you're looking at a feature.