Report 1 — TesseroRun · Jul 21

One run, told in four chapters. WarmList collected 612 posts from X, threw away 599 of them, scored the 12 that survived, and put 6 people in front of you. Every number below is followed by the evidence it came from.

Get Started

How this run narrowed down

The four chapters below, in one line — each step links to its evidence.

Collected612 100%Chapter 01 · 12 queries Passed screening460 75%Chapter 02 · 152 removed, rule by rule Scored as candidates12 2%Chapter 03 · 6 hot · 6 near-miss · 1 watch Ready to contact6 1%Chapter 04 · hot × contact-safe

Collected

What this run went looking for, and everything it dragged back before a single judgement was made.

612posts collected from 12 queries

The 12 queries built from your site

Built from tessero.example.com, searched on X. 9 produced candidates, 3 produced none.

Search query	Leads	Hot	Share
track client feedback	2	1	18%
client invoicing tool freelance	2	0	18%
cloverbook too expensive	1	1	9%
ondaro setup time	1	1	9%
losing client feedback email	1	1	9%
slatepad client tracker	1	1	9%
freelance CRM recommendation	1	1	9%
spreadsheet client management	1	0	9%
how do you track clients	1	0	9%
3 queries produced no candidates	0	0	—

One query, track client feedback, produced 2 of the 12 candidates and 1 of the 6 hot leads. The 3 that produced no candidate are the cheapest thing to change before the next run.

Run scope

The reach behind the 612.

Run: Jul 21
Product: tessero.example.com
Sources: X
Search queries: 12 built from your site
Posts collected: 612
Candidate posts span: Jun 18 – Jul 20

When the 12 posted

Candidate posts per week across the 5-week span.

Jun 18Jul 2Jul 16

Candidate posts per week
Week of	Candidates
Jun 18	1
Jun 25	1
Jul 2	2
Jul 9	4
Jul 16	3

7 of 12 candidates posted in the final two weeks — this report is mostly fresh complaint, not archaeology.

Cleaned

The part of the run you never see. 599 posts were thrown away in two passes — here is which rule removed each batch.

460passed screening · 152 removed before scoring

Noise removed

All 612 collected posts, by what happened to them.

599removed for you · 152 screened · 447 low-fit

612 collected12 candidates

Screened out before scoringNever worth a scoring call — noise rules and duplicate posts.Company accounts 44Duplicate posts 41Promotional posts 30Outside the run window 16Bot network posts 12Link-only posts 9152

Low-fitScored, but landed below the candidate bar. Removed after scoring.447

Watch-onlyReal pain, flagged do-not-contact — market intel, not an outreach target.1

Survived to Chapter 03The candidates you actually read.12

The cut happens in two passes: 152 screened out before scoring, 447 more after. Near-misses are not counted as noise — all 6 are still in Chapter 03, one condition away from hot.

Inside the 152

What the pre-scoring screen removed, and what reached the scorer.

Collected from X612

−Company accountsBrand or product accounts, not a person with the problem.44

−Duplicate postsSame post reached by more than one query.41

−Promotional postsSomeone selling, not someone hurting.30

−Outside the run windowPosted before the lookback window began, or has no readable post date.16

−Bot network postsThe same wording posted by two or more different accounts — the whole set removed.12

−Link-only postsJust a URL or whitespace — no words of its own to read.9

=Reached the scorer460

The run keeps a count per rule, not the handles behind them — so this chapter names the rule that fired, never the account it removed.

612 collected− 152 screened out=460 passed screening

Chosen

12 posts scored against your rubric. The category decides what you do with each one; the score out of 100 is the evidence behind the category.

12candidates · 6 hot · 6 near-miss · 1 watch alongside

The full slate

All 12 candidates, ranked, each with the 100-point bar that produced its score · the rule marks the hot floor of 65.

#	Person	Found by	Category	Score
1	Mira Designs@mira_example	cloverbook too expensive	hot	87/100
2	Studio Marlo@marlo_example	ondaro setup time	hot	79/100
3	Davey Builds@davey_example	losing client feedback email	hot	74/100
4	Pixel and Ink@pixel_example	slatepad client tracker	hot	71/100
5	Nora Type@nora_example	track client feedback	hot	68/100
6	Quiet Studio@quiet_example	freelance CRM recommendation	hot	66/100
7	Casetype@casetype_example	spreadsheet client management	near-miss	63/100
8	Ravi Makes@ravi_example	client invoicing tool freelance	near-miss	58/100
9	Lena Letters@lena_example	client invoicing tool freelance	near-miss	52/100
10	Hollow Press@hollow_example	how do you track clients	near-miss	47/100
11	MKW Dev@mkw_example	track client feedback	near-miss	41/100

Score composition, all 12 candidates (points out of 100)
Candidate	Score composition	Not earned	Total
Mira Designs	Pain fit 38 of 40, Buying stage 20 of 20, Buyer 12 of 20, Freshness 17 of 20	13	87
Studio Marlo	Pain fit 30 of 40, Buying stage 20 of 20, Buyer 11 of 20, Freshness 18 of 20	21	79
Davey Builds	Pain fit 32 of 40, Buying stage 14 of 20, Buyer 12 of 20, Freshness 16 of 20	26	74
Pixel and Ink	Pain fit 30 of 40, Buying stage 12 of 20, Buyer 15 of 20, Freshness 14 of 20	29	71
Nora Type	Pain fit 28 of 40, Buying stage 12 of 20, Buyer 12 of 20, Freshness 16 of 20	32	68
Quiet Studio	Pain fit 26 of 40, Buying stage 12 of 20, Buyer 13 of 20, Freshness 15 of 20	34	66
Casetype	Pain fit 24 of 40, Buying stage 20 of 20, Buyer 7 of 20, Freshness 12 of 20	37	63
Ravi Makes	Pain fit 25 of 40, Buying stage 10 of 20, Buyer 10 of 20, Freshness 13 of 20	42	58
Lena Letters	Pain fit 22 of 40, Buying stage 8 of 20, Buyer 11 of 20, Freshness 11 of 20	48	52
Hollow Press	Pain fit 18 of 40, Buying stage 10 of 20, Buyer 10 of 20, Freshness 9 of 20	53	47
MKW Dev	Pain fit 21 of 40, Buying stage 9 of 20, Buyer 4 of 20, Freshness 7 of 20	59	41

The 6 hot leads run from 66 to 87 out of 100 — a tight band, not one runaway. Read down the bars and the pattern repeats: Pain fit carries the score — 42% of every point this slate earned — while buyer is where it gives the most back, at 53% of that axis’s maximum.

Score distribution

All 12 candidates this run · scores out of 100.

6of 12 candidates ≥ 65

hot ≥ 65belowlowest hot this run: 66

4050607080

Candidate score distribution
Score bucket	Candidates
40–49	2
50–59	2
60–69	3
70–79	3
80–89	1

Buying stage

How ready this slate is to buy · from the scoring rubric.

Complaining about a competitor3

Problem-aware8

Not problem-aware yet0

3 of 12 are already naming a competitor’s product as the problem — the shortest distance between a post and a reply.

The 5 that stopped short

Near-misses, with the bar that fell short of 65 and every condition they were missing — not just the first one.

Casetype@casetype_examplenear-miss63/100

63 · 2 short of hot

Buying stage is maxed by the named competitor, but the post says nothing about who they run projects for, so the buyer axis gives most of its points back.

What’s missing

A multiple-client workload
Evidence they choose and pay for their own tools

Ravi Makes@ravi_examplenear-miss58/100

58 · 7 short of hot

Real, recent invoicing pain — but invoicing alone is one feature of the problem, and nothing sizes their client load.

What’s missing

A multiple-client workload

Lena Letters@lena_examplenear-miss52/100

52 · 13 short of hot

The pain is real but narrow — invoice design, not project tracking — and nothing on the account suggests more than one client at a time.

What’s missing

A multiple-client workload
A named tool they have already outgrown

Hollow Press@hollow_examplenear-miss47/100

47 · 18 short of hot

An adjacent problem scored honestly: scheduling chaos is real pain in the right profession, but it is not the pain this product removes.

What’s missing

The core problem this product solves — project and feedback tracking

MKW Dev@mkw_examplenear-miss41/100

41 · 24 short of hot

The problem fits — scattered client work, named exactly — but the buyer axis all but empties out: this is a developer, not the designer the rubric is looking for.

What’s missing

The target profession — a designer, not a developer

3 of the 5 are missing the same thing — A multiple-client workload. That is the condition to watch for next run, not a reason to write them off.

Also worth knowing Watch · do-not-contact

One post cleared the pain bar but is not an outreach target. Delivered as market intel.

Fern & Pixel@fern_example X · Jul 17watch82/100

82 would have cleared hot — the contact-safe check is what stops it, not the score

@fern_exampleon X · Jul 17

I built a Slatepad CRM for my design clients and I already hate maintaining it. Every project update means editing 3 databases.

31487View original ↗

WHY WE FLAGGED THEM

Their account sells the client-tracking templates they are complaining about maintaining. They are building in this market, not shopping in it, so a pitch would land as a rival’s. Delivered as market intel instead.

OUR READ

Already built a homemade CRM and is frustrated by upkeep — exactly the "outgrew the DIY setup" moment your product solves.

A score you should not contact is still worth reading: it is the clearest description of the problem in this run, written by someone who solved it themselves.

460 passed− 447 low-fit− 1 watch-only=12 candidates

Act

What the whole run was for: 6 people you can message today, each with the post that qualified them and the bar that scored them.

6ready to contact today · hot × contact-safe

How to read a score bar

Axis maxima and both thresholds come from this report’s rubric version — not from this page.

Pain fitup to 40

Buying stageup to 20

Buyerup to 20

Freshnessup to 20

Not earned — the points this post did not makecloses at 100

Each bar below is the whole 100-point rubric, not a percentage. A post’s axis blocks sit at their true share of 100 and the hatch closes the bar, so the segments you can see and the points that were missed always add up to 100.

Two rules cross every bar: near-miss at 35 and hot at 65. A lead is hot because its coloured blocks reach past the second rule — the category is a fact about the picture, not a separate opinion.

Pain fit 40 · Buying stage 20 · Buyer 20 · Freshness 20 · total 100

Mira Designs@mira_example · X · Jul 18

#1 of 12HOT · CONTACT-SAFE

@mira_exampleon X · Jul 18

Cloverbook just raised prices again. $39/mo to send invoices and track 4 clients is insane. What are you all using?

246118View original ↗

WHY WE PICKED THEM

Direct pricing complaint about a competitor and actively asking for alternatives — a buying-intent signal, not a vague gripe. Names a 4-client workload, which matches the ICP.

Found by cloverbook too expensive · ranked #1 of 12 candidates · 612 posts scanned

WHY THIS SCORE

87/ 100hot ≥ 65 · cleared by +22

38+20+12+17=87

Pain fit 38/40Buying stage 20/20Buyer 12/20Freshness 17/20Not earned 13/100

Names the competitor, names the price and asks the room for an alternative — the buying-stage axis is maxed because the post is the switch decision itself.

Studio Marlo@marlo_example · X · Jul 20

#2 of 12HOT · CONTACT-SAFE

@marlo_exampleon X · Jul 20

Ondaro has been sitting half-configured for three weeks. I just want to send an invoice and move on.

9244View original ↗

WHY WE PICKED THEM

Three weeks into a setup they never finished, and the thing they actually want — send an invoice, get back to work — is the whole job your product does on day one. A stalled competitor rollout is the cheapest switch to win.

Found by ondaro setup time · ranked #2 of 12 candidates · 612 posts scanned

WHY THIS SCORE

79/ 100hot ≥ 65 · cleared by +14

30+20+11+18=79

Pain fit 30/40Buying stage 20/20Buyer 11/20Freshness 18/20Not earned 21/100

Full buying-stage points for naming the tool that is failing them; pain fit is a little short because the post describes the setup, not the day-to-day loss.

Davey Builds@davey_example · X · Jul 16

#3 of 12HOT · CONTACT-SAFE

@davey_exampleon X · Jul 16

Lost a client’s feedback in a 200-message email thread again. There has to be a better way to run a 1-person studio.

17396View original ↗

WHY WE PICKED THEM

Names the exact pain — feedback lost in email — and self-identifies as a solo studio, your core ICP.

Found by losing client feedback email · ranked #3 of 12 candidates · 612 posts scanned

WHY THIS SCORE

74/ 100hot ≥ 65 · cleared by +9

32+14+12+16=74

Pain fit 32/40Buying stage 14/20Buyer 12/20Freshness 16/20Not earned 26/100

Strong pain fit — the lost-feedback thread is the exact problem — but they are describing the symptom, not shopping yet, so buying stage lands mid-band.

Pixel and Ink@pixel_example · X · Jul 11

#4 of 12HOT · CONTACT-SAFE

@pixel_exampleon X · Jul 11

Every new client I re-invent my whole tracking system in Slatepad. It never survives past month two.

12139View original ↗

WHY WE PICKED THEM

They rebuild their tracking system for every new client and watch it collapse by month two. That is the "my own setup keeps failing" moment that comes right before someone pays for a real one.

Found by slatepad client tracker · ranked #4 of 12 candidates · 612 posts scanned

WHY THIS SCORE

71/ 100hot ≥ 65 · cleared by +6

30+12+15+14=71

Pain fit 30/40Buying stage 12/20Buyer 15/20Freshness 14/20Not earned 29/100

Repeat-failure pain scores well; nothing in the post names a tool they would be leaving, which is what keeps buying stage down.

Nora Type@nora_example · X · Jul 15

#5 of 12HOT · CONTACT-SAFE

@nora_exampleon X · Jul 15

Anyone else keep a client’s revision notes in six different places? Figma comments, email, DMs, a Slatepad doc.

21263View original ↗

WHY WE PICKED THEM

Revision notes spread across four places, listed by name. They are describing the scattered-feedback problem precisely enough that a reply can quote it back to them.

Found by track client feedback · ranked #5 of 12 candidates · 612 posts scanned

WHY THIS SCORE

68/ 100hot ≥ 65 · cleared by +3

28+12+12+16=68

Pain fit 28/40Buying stage 12/20Buyer 12/20Freshness 16/20Not earned 32/100

Clears hot on pain fit and a recent post date; the "anyone else" framing is a complaint, not a search, so buying stage stays mid-band.

Quiet Studio@quiet_example · X · Jul 13

#6 of 12HOT · CONTACT-SAFE

@quiet_exampleon X · Jul 13

What do you actually use to keep track of client projects? Spreadsheets are killing me but everything else is bloated.

43571View original ↗

WHY WE PICKED THEM

Open question asking for recommendations, with the "bloated tools" objection your lightweight positioning answers directly.

Found by freelance CRM recommendation · ranked #6 of 12 candidates · 612 posts scanned

WHY THIS SCORE

66/ 100hot ≥ 65 · cleared by +1

26+12+13+15=66

Pain fit 26/40Buying stage 12/20Buyer 13/20Freshness 15/20Not earned 34/100

Just clears the hot floor: a real request for recommendations, with the "everything else is bloated" objection your positioning answers, but no tool named as the one being replaced.

What this run leaves you

The last chapter is the one WarmList cannot write.

1.0%market temperature · 6 hot out of 612 posts scanned

One run is a reading, not a trend. Once a second run lands, this becomes the line you watch week over week.

612 posts read, 599 discarded, 12 scored, 6 people worth your morning — all of them cleared the contact-safe check. The next number in this story is the one you write.

12 candidates− 6 near-miss=6hot, all contact-safe

End of run · Jul 21 · Tessero · scores out of 100 · hot ≥ 65

Candidate counts and scores are estimates from public posts — a guide, not a guarantee. You decide who to contact.

Run this on your own product

Paste your URL. WarmList scans at least 500 public posts on X, scores every one of them against your product, and hands you a report exactly like this one — with real people in it.

Get Started

$9 for one report · typically ready in about 10 minutes