> ## Documentation Index
> Fetch the complete documentation index at: https://wiki.jamesvarga.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Paid traction versus activity metrics in fintech

> How to distinguish real commercial traction from vanity activity in fintech go-to-market — and why the difference determines survival.

Paid traction is revenue or contractually committed spend from a buyer who has completed procurement, signed terms, and is paying for the product. It is the only reliable signal that a fintech has achieved product-market fit in a regulated market.

Most early-stage fintechs report activity metrics — meetings held, demos given, pilots running, LOIs signed — as evidence of commercial progress. These signals feel like traction but predict nothing. Paid traction is the dividing line between companies that are selling and companies that are performing.

## Why does the distinction matter in fintech?

In consumer SaaS, activity metrics can correlate with traction. High sign-up rates lead to paid conversions in predictable ratios. In fintech, the correlation breaks down because:

* **Regulated buyers explore without buying.** Innovation teams at banks run pilots, attend demos, and sign memoranda of understanding with no procurement authority or allocated budget.
* **Free pilots do not convert automatically.** A successful free pilot proves the product works. It does not prove the buyer will pay. The conversion from free pilot to paid contract requires a separate procurement process that many fintechs do not plan for.
* **LOIs and MOUs are not contracts.** Letters of intent and memoranda of understanding carry no financial commitment. They are signals of interest, not signals of revenue.
* **Long sales cycles mask stalls.** In a 12-month sales cycle, a deal that stalled at month 3 can look identical to a deal that is progressing at month 3. Without traction signals, the team cannot distinguish the two.

The Scottish Scale-Up Panel identified that between 2001 and 2016, more than 40% of Scotland's high-growth firms were acquired or closed. One contributing factor: companies reported activity as progress, raised capital against vanity metrics, and ran out of runway before converting pilots to contracts.

## What counts as paid traction?

Paid traction signals are commitments where money changes hands under agreed commercial terms.

**Real traction signals:**

* Signed contract with defined payment terms
* Paid pilot with a budget holder and conversion criteria
* Recurring revenue from a production deployment
* Purchase order issued by procurement (not the innovation team)
* Committed annual contract value with a start date

**Activity signals that are not traction:**

* Meetings with interested buyers
* Product demos to innovation teams
* Free or unpaid pilots with no conversion terms
* Signed NDAs
* Letters of intent or memoranda of understanding
* Conference presentations to potential buyers
* Mentions in a bank's innovation report
* Partnership announcements without commercial terms

The dividing line is simple: has procurement approved the spend, and is money moving? If the answer to either is no, it is activity, not traction.

## How should fintechs measure commercial progress?

Replace vanity dashboards with a progression framework that tracks where each deal sits in the [commercial sequence](/knowledge/fintech-gtm/commercial-sequencing).

| Stage                   | Signal                                                                 | What it proves                                              |
| ----------------------- | ---------------------------------------------------------------------- | ----------------------------------------------------------- |
| **Qualified interest**  | Named buyer with confirmed budget and use case                         | Someone wants to buy, not just explore                      |
| **Evidence submitted**  | Evidence pack sent and vendor questionnaire completed                  | The buyer is progressing through internal gates             |
| **Pilot running**       | Paid or time-bound pilot with success criteria and named budget holder | The product is being tested under real conditions           |
| **Assurance cleared**   | Risk, IT security, and compliance teams have approved                  | The vendor is acceptable to the bank's internal gatekeepers |
| **Contract signed**     | Procurement has issued terms and payment is scheduled                  | Revenue is committed                                        |
| **Production deployed** | The product is live in the buyer's production environment              | The product works at scale in a real banking environment    |

Track the number of accounts at each stage, the time spent at each stage, and the conversion rate between stages. A healthy pipeline shows consistent movement from left to right. A stalled pipeline shows accounts piling up at one stage.

## What causes the gap between pilots and paid contracts?

The pilot-to-production gap is the most common failure point in fintech GTM. Fintechs run successful pilots but cannot convert them to production contracts.

Four structural causes:

1. **No budget allocation.** The innovation team funded the pilot from a discretionary budget. Production deployment requires business-line budget that was never allocated.
2. **Procurement cannot process it.** The bank's procurement framework has minimum vendor requirements (trading history, revenue thresholds, insurance minimums) that the fintech does not meet.
3. **Risk team was not involved.** The pilot ran without risk approval. When the conversion request reaches risk, they start a full review from scratch.
4. **Success criteria were never defined.** Without agreed metrics, the pilot has no basis for a conversion decision. It drifts into a permanent trial.

These failures are preventable. See [why pilots fail to become production contracts](/knowledge/procurement/pilot-to-production) for detailed analysis and prevention methods.

## How should fintechs design pilots that convert?

Pilot design determines conversion probability. A well-designed pilot is a structured step toward a paid contract, not an open-ended product trial.

1. **Agree success criteria before the pilot starts.** Define 2 to 3 measurable outcomes. Both parties sign off.
2. **Name the budget holder.** The person who will approve the production contract must be identified and engaged before the pilot begins.
3. **Set a time limit.** 4 to 8 weeks is sufficient for most fintech pilots. Longer than 12 weeks and the pilot loses urgency.
4. **Charge for the pilot.** Even a nominal fee (£5,000 to £25,000) validates that the buyer treats this as a procurement decision, not an innovation experiment.
5. **Run assurance in parallel.** Submit the [evidence pack](/knowledge/procurement/evidence-packs) and vendor questionnaire while the pilot runs. If assurance completes before the pilot ends, the conversion decision is faster.
6. **Define exit terms.** What happens if the pilot succeeds? What happens if it fails? Both scenarios should be documented before the pilot starts.

## Common mistakes

* **Reporting activity as traction to investors and the board.** This misaligns expectations and delays the hard conversations about commercial readiness.
* **Running free pilots indefinitely.** A pilot without a deadline, a budget holder, and conversion criteria is not a pilot. It is free product usage.
* **Confusing partnership announcements with revenue.** Press releases about strategic partnerships generate visibility but not cash. Track the revenue, not the PR.
* **Measuring pipeline by volume, not stage.** 50 accounts at the "interested" stage are worth less than 3 accounts at the "assurance cleared" stage.
* **Delaying the pricing conversation.** Fintechs that wait until after the pilot to discuss pricing lose negotiating leverage. Pricing should be part of the pilot agreement.
* **Treating every conversation as a lead.** A meeting with an innovation analyst is not a qualified lead. A meeting with a business-line budget holder who has confirmed the use case is a qualified lead.

## Key takeaways

* Paid traction means money moving under signed terms. Everything else is activity.
* Activity metrics predict nothing in regulated markets. Track progression through the commercial sequence instead.
* The pilot-to-production gap is the primary failure point. Design pilots with conversion terms before they start.
* Charge for pilots. Even a nominal fee validates procurement intent.
* Run assurance in parallel with the pilot. Sequential processing doubles the timeline.
* Measure pipeline by stage, not by volume. Three deals at contract stage are worth more than fifty at the interest stage.

## Related pages

* [How to sell fintech products to banks](/knowledge/fintech-gtm/selling-to-banks)
* [Commercial sequencing for fintech GTM](/knowledge/fintech-gtm/commercial-sequencing)
* [Fintech go-to-market knowledge](/knowledge/fintech-gtm/index)
* [Why pilots fail to become production contracts](/knowledge/procurement/pilot-to-production)
* [Evidence packs for procurement](/knowledge/procurement/evidence-packs)
* [GTM Benchmark](/frameworks/gtm-benchmark)
* [5 Days to Scale sprint](/frameworks/5-days-to-scale)
* [Closing Foundry](/companies/closing-foundry)
* [Export-first strategy for startups in small markets](/knowledge/ecosystem/export-first)
* [Public procurement as a startup growth engine](/knowledge/ecosystem/public-procurement-growth-engine)