The First 100 Customers Course #12: How Litix Turned 60 Districts Into a Statewide Trust Loop

TL;DR

Litix did not use an association endorsement to get its first school-district customers. It arrived at the association meeting with about 60 districts already using the product. Co-founder Mike Mastrullo says those accounts came mostly through word of mouth, supported by founder-led demos, very fast support, and a product built around work he had done for 20 years in education.

The first buyer was a former colleague who stopped the pitch and said she was in because she trusted him. That is useful access, but it is not a distribution system. The repeatable result came from converting borrowed founder trust into customer proof, converting customer proof into peer referrals, and then transferring accumulated trust to the Massachusetts Association of School Superintendents. Mastrullo says the association initially warned that it did not endorse vendors. After the presentation, its director asked how to get Litix into every district and subsidised part of the access.

Litix later reached 80–85% of Massachusetts districts, a range independently corroborated by the Massachusetts Municipal Association. The mechanism was insider problem knowledge → trusted first buyer → high-touch service → peer proof → local density → association validation → more trusted access. The warning is simple: a network can open the first door, but an institution will not rescue a product that customers do not recommend.

What you will build

You will build a 30-day trust loop for one narrow B2B market. The outputs are a buyer-and-workflow brief, ten interview records, a first-account evidence contract, a manual-service ledger, a peer introduction map, a partnership brief, and a weekly scorecard. Each stage has a pass condition and a stop condition, because “relationship driven” becomes vague unless you can see what trust did next.

Who this is for

Use this model for vertical SaaS, regulated workflows, professional services converted into software, and AI products sold into a small buyer community. It fits when buyers consult peers, meet inside associations or regional groups, and care more about operational credibility than broad social proof. The founder must still be able to speak with every early account.

Do not use it when the buyer category has no shared institution, the product outcome cannot be safely discussed, or implementation requires months before anyone sees value. Do not use it as permission to sell only to friends. Friendly accounts can expose the workflow, but unfamiliar buyers must eventually choose the result without relying on a personal relationship.

Case snapshot

Stage	What happened	Evidence limit
Founder context	20 years in education, including 16 as a principal	Founder statement; episode introductions vary
First product wedge	Compliance training funded development of the harder analytics product	No launch dates disclosed
First buyer	A former colleague accepted before the pitch finished	Name, date, district, price and invoice undisclosed
Before MASS	About 60 school districts	Founder-reported approximate count
Demo conversion	About 70%	Founder estimate; explicitly not an exact metric
Massachusetts adoption	80–85% of districts	MMA sources support the range at different dates
Retention	97%	Period and denominator not published
Current scale	300+ districts	Later company and association claim, not early attribution

The model: prove trust before you amplify it

Mastrullo had unusual founder-market fit. As a principal, he had managed budgets and sat at bargaining tables. He saw volunteer school boards negotiating large labour budgets with little comparable data while the other side arrived with more specialised resources. His co-founder, John Boynton, heard the idea during a conversation at a baseball game and offered to become the first investor if Mastrullo built it.

That background created relevance and access. It did not remove selling. In the Life's a Pitch interview, Mastrullo describes former superintendents and business officers who act as “door openers.” Even they are surprised when contacts ignore their messages. A network may produce a meeting, but it does not guarantee one, and it certainly does not guarantee a purchase.

Litix made trust portable in three ways. It sold a concrete job instead of a data platform. It responded to customers in minutes and sometimes accepted requests that the team knew would not scale. And it kept changing the product around customer needs. In a tightly connected public school market, customers then carried the story to peers. The association partnership came after this local proof existed.

Step 1: choose a trust-dense market

“Education” is not a usable first market. Litix narrowed the buyer by geography and role. In Massachusetts the superintendent commonly buys; in California the chief business official is central; municipal buyers may be a town manager or HR leader. The workflow was also specific: prepare salary, benefits and settlement evidence for collective bargaining, or complete mandatory training without chasing staff through spreadsheets.

Complete this market worksheet before you build a prospect list:

• Buyer: one role with budget or implementation authority.
• High-stakes job: one recurring decision where delay or error carries a cost.
• Current workaround: spreadsheet, manual research, generic tool or consultant.
• Peer graph: where buyers compare notes before they choose.
• Proof unit: the result one buyer can safely explain to another.

Interview ten buyers. Ask what triggered the last search for help, how the work happens today, who approves a change, and whom they call for advice. Do not pitch during the first half of the call. The output is a problem ledger, not ten compliments.

Pass condition: at least seven buyers describe the same job, workaround and peer group. Stop condition: every buyer requires a different product or nobody can name a trusted peer or institution.

Step 2: turn the first friendly account into evidence

Litix's first buyer reportedly said yes because she had worked with Mastrullo. The honest lesson is not to celebrate the conversion. It is to separate relationship risk from product evidence. A friend can tolerate an unfinished interface, incomplete procurement material or founder labour that a stranger would reject.

Create a one-page evidence contract with the first account:

1. Record the current workflow, elapsed time and failure cost.
2. Name one live job the product must complete.
3. Log every manual founder action required to reach the result.
4. Schedule a review date before onboarding begins.
5. Agree what may be shared with one peer, with the customer's approval.

Do not invent an ROI figure when the baseline is missing. Mastrullo says buyers understand a promise such as saving 50 hours, but the interview does not provide measured customer time studies. Treat that number as positioning until your own account supplies a before-and-after record.

Pass condition: one real workflow completes and the buyer agrees to a reference check-in. Stop condition: the account only wants unrelated custom labour or cannot define a useful result.

Step 3: make manual service visible

Litix reports support response in minutes and seconds. Mastrullo also describes accepting work that cannot scale because the customer will be delighted and tell peers. That can be rational at ten accounts and dangerous at one hundred. The difference is whether the founder can see the cost and convert repetition into a product decision.

Keep a manual-work ledger with six fields:

• request and customer segment;
• trigger and promised outcome;
• owner and minutes spent;
• customer result;
• number of previous occurrences;
• template, build, decline or keep-manual decision.

Template work after three repetitions. Build or remove it after ten. Decline one-offs with no retained customer value. Never improvise safety, privacy or compliance work merely to appear responsive. A service promise should protect the core workflow, not hide a broken product.

Pass condition: manual work creates product learning or a referenceable outcome. Stop condition: service absorbs the week without improving activation, retention or the product.

Step 4: ask for one relevant peer

Mastrullo says peer recommendation matters more than the association endorsement in K-12. That does not mean asking every customer for a testimonial. A testimonial stays on your page. A peer introduction transfers trust into a real buying conversation.

You solved [job] with [result]. Which peer is facing the same decision this quarter? If it is useful, introduce us around the workflow, not the product.

Track the source account, introduced role, shared workflow, meeting and outcome. Keep referred accounts separate from friendly accounts and cold prospects. Otherwise a blended conversion rate hides whether trust is actually travelling.

Pass condition: three of ten retained accounts introduce one relevant peer. Stop condition: customers renew but will not take a reference call. Investigate outcome quality and relationship safety before adding prospect volume.

Step 5: approach the institution after density

Litix approached the Massachusetts Association of School Superintendents when it was already working with about 60 districts. According to Mastrullo, the executive director opened by saying the association did not partner with or endorse vendors. Five minutes into a planned 30-minute presentation, he stopped it and asked how they could get Litix into every district. The association later subsidised access.

This meeting is founder-reported and the subsidy terms are not public. The larger adoption is easier to verify. An MMA Beacon article said Litix worked with more than 80% of Massachusetts districts in May 2025. A later MMA report said 85% and described how the same association pattern expanded into municipalities.

Build a one-page partnership brief:

• member problem and the affected role;
• number of existing member customers;
• three outcomes with explicit evidence limits;
• support, data-use and procurement model;
• the exact member benefit;
• one requested distribution action;
• endorsement, exclusivity and conflict boundaries.

Ask for a pilot cohort, member education session, negotiated access or a standard workflow. Do not ask for a logo and call it distribution. The partner must connect evidence to trusted member access.

Pass condition: the institution names the member benefit, decision owner and next action. Stop condition: it offers visibility without access, or asks for unsupported claims or exclusivity.

What failed, and what remains unproven

First, the network was weaker than it appeared. Door openers with close relationships still had messages ignored. Second, cold email and LinkedIn met strong public-sector scepticism and slow procurement. Third, conferences created an opportunity to show customer density, but Mastrullo admits that he used to avoid vendors when he attended from the buyer side.

The numbers also have limits. Mastrullo estimates that roughly 70% of demos convert, then says the company does not have an exact metric. The reported 97% retention appears on Litix's current site and association partner pages, but no denominator, period or logo-versus-revenue definition is published. There is no disclosed price, CAC, contract value, sales-cycle duration or payback. A useful course must preserve those blanks.

Your 30-day implementation plan

Days	Work	Required output	Gate
1–7	Choose one buyer and workflow; run ten interviews	Problem ledger and peer map	7/10 share the job and workaround
8–14	Recruit one live account and baseline the work	Evidence contract and manual ledger	One real workflow completes
15–21	Onboard up to nine more accounts; request peers after value	Reference map and objection ledger	3 introductions from 10 retained accounts
22–30	Draft and test one partnership brief	Member benefit, evidence and requested action	Proceed only with customer density

At day 30, choose one of three decisions. Continue the loop if retained accounts refer peers. Return to activation if customers stay but will not recommend. Narrow or stop if the accounts need different products and no trusted group connects them. Never approach more institutions to compensate for weak customer proof.

Lead Scorer implementation

This motion fits Lead Scorer when the audience is small, research quality matters and every external action needs human approval. The tool can organise the manual research, qualification and drafting loop. It cannot create customer trust, guarantee an endorsement or send without review.

1. Store the boundaries

Use the icp-offer-context skill to record the product, buyer role, disqualifiers, supported outcomes and claims you may not make. Keep three lists: friendly or design-partner accounts, referred peers, and institution-sourced audiences. This separation protects channel attribution.

Agent prompt: “Define one ICP for [workflow] in [market]. Exclude [three cases]. Treat customer count, retention and ROI as unusable unless a source is attached.”

2. Research before enrichment

Run signal-research-dossier for dated evidence about each operator and institution. Apply icp-scoring-rubric before spending contact-discovery credits. For a small trust experiment, keep only scores of 8/10 or higher. A company match is insufficient if the person does not own the workflow or participate in the peer graph.

Pass: two dated signals, role ownership and an explicit reason the account belongs in this list. Stop: no verifiable role or only generic company news.

3. Draft with approval gates

Use contact-discovery only for approved keepers. Draft a first touch with cold-email-first-touch or a connection note with linkedin-connection-requests. Run outreach-qa-audit over every draft. A human must check the evidence, claim and ask before a campaign is activated.

Agent prompt: “Draft one message around the verified workflow signal. Do not imply endorsement, customer results or a relationship we do not have. Ask for a short problem conversation. Leave every message in draft.”

4. Turn objections into the next trust asset

Classify replies and objections. Store repeated questions in Content Studio with the source. Publish useful evidence only after review, then qualify people who visibly engage as a separate signal audience. The loop is research → draft → human approval → reply → useful evidence → new qualified signal, not mass outreach followed by automated sending.

Saveable checklist

• One buyer role, one high-stakes workflow and one peer graph.
• Ten interviews; seven must share the job and workaround.
• One live account with a baseline, review date and evidence boundary.
• A manual-work ledger with template, build, decline and keep-manual decisions.
• Three relevant peer introductions from ten retained accounts.
• Customer density before institution outreach.
• A partnership brief with member benefit and one requested action.
• Separate lists for friendly, referred and institution-sourced accounts.
• Score before enrichment; human review before every external action.
• No invented CAC, ROI, conversion or retention definition.

Sources and limits

The primary narrative comes from Mastrullo's June 25, 2026 podcast interview. Litix's episode recap and about page confirm the founder context, product focus and current company claims. The NHSAA partner page independently repeats the current 300+ district and 97% retention claims.

The first buyer, first-60 count, “mostly word of mouth” attribution, original association meeting, subsidy and estimated 70% demo conversion remain founder-reported. The MMA sources independently support later 80–85% Massachusetts adoption, not the source of each early account. No source found provides the first buyer's name, early pricing, revenue, CAC, sales-cycle duration or audited retention. The course therefore teaches sequence and decision gates, not a financial forecast.