Free ICP generator / SaaS
Ideal customer profile for a SaaS company
A SaaS ICP has a job most profiles don't: it has to predict who stays, not just who signs up. A trial sign-up costs you nothing to win and a lot to serve if they were never going to pay. So the useful lines are the ones that separate payers from tourists: the company size where your pricing makes sense, the person who owns the budget (often not the user), and the event that makes them look now (a new hire, an audit, a renewal on a tool they hate). Disqualifiers matter more here than anywhere: they're the sign-ups who will churn in month two. Below is a worked example for Corvantle, a fictional contract-renewal tool. Each line points to the page on its invented site it came from, the way the generator does for yours.
Corvantle corvantle.example
Contract and renewal tracking software for finance teams. Corvantle is a fictional SaaS company. Its site is invented so the generator has something to read; yours fills in here.
Finance-led companies with 100 to 500 staff
Best fit: pricing and 2 case studies- Who they areUS companies with 100 to 500 staff and 40+ software subscriptions, with no procurement team.From /pricing
- Who decidesThe controller or VP Finance. IT signs off on single sign-on.From /customers/halvard-freight
- Their painRenewals found on the credit card statement after they've already auto-renewed.From /
- What sets them offBudget season, a surprise auto-renewal over $20k, or a new CFO asking "what do we pay for?".From /customers/halvard-freight
- Who to skipCompanies under 50 staff (too few contracts) and companies with a procurement department on an enterprise suite.From /pricing
- Where they areFinance-leader communities and the accounting-software marketplaces Corvantle lists in.Inferred from/integrations
Startups after a Series A, 40 to 150 staff
Strong fit: 1 case study- Who they areVenture-backed software companies that doubled headcount in a year and now pay for tools team by team.From /customers/pinemark
- Who decidesThe head of finance, often hired in the last six months.From /customers/pinemark
- Their painDuplicate tools bought by different teams, and no single list of what's owed when.From /customers/pinemark
- What sets them offThe first board meeting that asks about burn, or preparing for a SOC 2 audit's vendor list.Inferred from/blog/vendor-list-for-soc2
- Who to skipPre-revenue startups with under 20 tools.From /pricing
- Where they areStartup finance newsletters and the founders' investors' portfolio perks pages.Inferred from/about
Legal operations teams at mid-size firms
Test group: 1 blog post- Who they areIn-house legal teams of 2 to 10 people managing customer and vendor contracts.From /blog/legal-ops-renewals
- Who decidesThe general counsel.From /blog/legal-ops-renewals
- Their painNotice periods missed because dates live in PDFs.From /blog/legal-ops-renewals
- What sets them offA missed cancellation window.From /blog/legal-ops-renewals
- Who to skipTeams already on a full contract-lifecycle system.Inferred
- Where they areLegal operations associations and their newsletters.Inferred
Positioning check
The homepage says "for every team that buys software", but both case studies and the pricing page point to finance leaders at 100–500 person companies. Lead with finance. Legal operations has only one blog post behind it: treat it as a test, not a headline.
Now do yours
Same table, built from your own website. Group 1 is free, no email.
Questions
What should a SaaS ICP include?
Company size and type, the budget owner (not just the user), the pain in their words, the trigger that makes them look now, and disqualifiers: the sign-ups who won't pay or will churn. Add where they spend time so you know where to show up.
How do I know my ICP is right?
Check it against your paying customers, not your sign-ups. If most of your revenue comes from a group your ICP doesn't name, rewrite it. Revisit it every quarter while you're early.
Should a SaaS company have more than one ICP?
Usually one main group and one or two you're testing. Label the tests as tests. Splitting effort evenly across three groups is how early teams stall.