Benchmarks / SurveyBench / Why Tallyroom trials don't convert / Inkling 2 Mini
Inkling 2 Mini: Why Tallyroom trials don't convert
The decision: where to put next quarter's product and sales effort to lift trial-to-paid conversion: a new accounting integration, assisted setup, a cheaper plan, or a shorter trial. The brief and the data →
- Verdict
- ✗ Not sound
- Research score
- 74 of 100
- Analysis rating
- 567
- Head to head, this task
- won 9 of 14
Why it is not sound
The survey
- A research objective no question serves
- A leading question: Q9
- A double-barrelled question: Q7
The analysis
- Reported a material finding the data does not support
- Missed a trap: Only teams that did not pay were surveyed, so the survey cannot show what distinguishes them from teams that did; paying teams may also have struggled with setup.
Findings the judges found unsupported
Accounting-software support, especially Sage, is a real conversion lever, not a marginal preference. Prioritise Sage-first integration rather than trial-length changes.
The evidence establishes reported demand for Sage, not that integration is a proven conversion lever. Calling it one with high confidence goes beyond self-reported barriers and hypothetical purchase intentions.Connection likelihood is strongest for teams blocked by missing integration; this is the best next quarterly opportunity for making lapsed trials pay.
Higher hypothetical payment likelihood among integration-blocked respondents does not establish integration as the best quarterly conversion opportunity. The survey does not compare intervention effects or costs, and setup is the most common main reason after size weighting.
Scorecard
Numbers 11 of 11 right
| Question | Its answer | True | |
|---|---|---|---|
| What percentage of respondents said they would need a Sage integration before paying? | ✓ | 23.7% | 23.7% |
| Weighted to the company-size mix of all lapsed trials, what percentage would need a Sage integration? | ✓ | 18.1% | 18.2% |
| Among businesses with 1-9 employees, what percentage gave 'didn't have time to set it up' as the main reason? | ✓ | 27.4% | 27.4% |
| How many of the open-text answers mention not having time to set Tallyroom up, or setup taking too long? | ✓ | 24 | 24 |
| What is the 95% margin of error, in percentage points, on the unweighted share of respondents needing a Sage integration? | ✓ | 3.9 points | 3.89 points |
| Is the difference in the share giving 'too expensive' as their main reason between businesses with 1-9 employees and those with 50-249 statistically significant at the 95% level? (1 for yes, 0 for no) | ✓ | No | No |
| Weighted to the company-size mix of all 1,640 lapsed trials, about how many teams' main reason was not having time to set it up? | ✓ | 355 | 355 |
| How many of the open-text answers from businesses with 1-9 employees mention not having time to set Tallyroom up, or setup taking too long? | ✓ | 14 | 14 |
| Weighted to the company-size mix of all lapsed trials, what percentage would give 'no integration with our accounting software' as their main reason? | ✓ | 16.3% | 16.3% |
| What percentage of the trial admins invited completed the survey? | ✓ | 28% | 28% |
| Among respondents whose main reason was no integration with their accounting software, what percentage said they would be likely (fairly or very) to pay if Tallyroom connected to it? | ✓ | 61.3% | 61.3% |
Traps in the data 6 of 7 handled
- ✓Teams on 'Other' accounting software (base 17) mostly cite missing integration.
- ✓Teams of 50-249 people are 22% of respondents but 10% of lapsed trials. They cite missing integration and use Sage far more, so unweighted figures overstate integration and Sage demand and understate setup time: unweighted, missing integration is the top reason; weighted, setup time is.
- ✓Q2 is multi-select: percentages are of respondents and add up to more than 100%.
- ✓Likelihood to pay is a hypothetical stated intention.
- ✓The head of sales believes the trial is too long and teams forget about it.
- ✓460 of 1,640 invited admins completed (about 28%), with a £10 voucher; those who respond may differ from those who do not.
- ✗Only teams that did not pay were surveyed, so the survey cannot show what distinguishes them from teams that did; paying teams may also have struggled with setup.
The analysis
Next quarter: put effort into Sage-first accounting integration plus assisted setup, not into cutting the 30-day trial. Do not shorten the trial to 14 days: only 3.7% forgot it and 0.2% called it too long, while small firms cite missing time to finish setup. For Sage-blocked and 10-49/50-249-blocked teams, prioritise integration (Sage is ~25.4% of completes; 85.5% of Sage users would need it before paying; size-weighted ≈18.1% of all lapsed trials). For small firms, pair this with guided/assisted onboarding; setup-related main reasons are 18.7% overall and 27.4% among 1-9 employees (≈21.6% weighted, ≈355 teams). Keep pricing as a bounded test: 20.4% would need per-company pricing, but price is not significantly better/worse by size and price-blocked teams show only 23.3% likely to pay at £6; test flat-rate/per-company for firms with many occasional users rather than cutting the price broadly. Direct stakeholder answers: sales - do not cut to 14; product - Sage demand is the clearest named unmet need; finance - if connected, expect around 37.6% of lapsed-trial teams to be likely to pay at £6/user/month overall, and 61.3% among teams blocked by missing integration, with non-integration-blocked teams materially lower.
Change priority if Sage integration fails/behind and conversion in Sage-blocked teams does not move (e.g. <~40% to paid or flat with low-touch control), or if the assisted-setup pilot lifts conversion substantially more than integration pilot. Change away from integration if actual pay-after-connection is far below the 61.3% stated-likelihood, or if 14-day/trial-reminder telemetry shows most teams genuinely forget and conversion improves with shorter trials. Change away from assisted setup if small-firm setup is not a conversion bottleneck (e.g. setup completion is not strongly predictive of paid conversion) or if small firms choose no-expense tools rather than pay for setup.
Findings
-
Accounting-software support, especially Sage, is a real conversion lever, not a marginal preference. Prioritise Sage-first integration rather than trial-length changes.
23.7% of all completes would need a Sage integration before paying; 85.5% of Sage users would need it; 58.1% of Sage users gave 'no integration' as the main reason. Size-weighted to all 1,640 lapsed trials, about 18.1% would need Sage. Base: 460 completes; 117 Sage-user respondents.
-
Connection likelihood is strongest for teams blocked by missing integration; this is the best next quarterly opportunity for making lapsed trials pay.
Q5 net likely/very likely = 61.3% among the 93 respondents whose main reason was no integration; overall net likely = 37.6% across 460. This is self-reported stated likelihood, not booked revenue.
-
Do not cut the trial to 14 days. Trial-length/forgetting is not the main blocker; missed setup time is.
Q2: trial too long 0.2%, forgotten trial 3.7%, trial too short 1.5%; Q2 setup reason = 18.7% overall, 27.4% for 1-9 employee firms, size-weighted ≈21.6% of 1,640 lapsed trials (~355 teams).
-
Assisted setup is a strong complement, especially for small firms; it is not a substitute for integration.
Setup mentions: 24 of 109 open-text answers, including 14 from 1-9 employee businesses; Q2 setup-time reasons: 27.4% small, 15.9% 10-49, 10.0% 50-249. Open text repeats missed setup, disrupted by busier-than-planned work, and 'ran out of trial before finishing'.
-
Price is a live blocker but not the strongest, and is not significantly worse in small firms alone.
Q2 too expensive = 15.9% overall; small = 19.0% vs 50-249 = 15.5%; z ≈ 0.75, p ≈ 0.44, not significant. Price-like open-text themes: 23 answers, concentrated in per-seat logic; Q5 likely pay if connected for price-blocked teams only 23.3%.
-
Approval/workflow mismatch is a real product constraint for growing and compliance-oriented teams, but smaller than setup/integration at the size-mix level.
Q2 approval-fit reason = 12.6% overall, 7.1% small, 12.1% 10-49, 21.8% 50-249; 22.0% of completes said custom approval chains would be needed; 15 open-text answers describe one/single-approver limits, batch sign-off, or outside-person approval.
-
Some small businesses simply do not need an expenses tool; do not spend sales effort on them.
Q2 'decided we didn't need it' = 10.0% overall, 13.7% small and 12.6% 10-49, 0.0% 50-249; 12 open-text answers say the low-expense reality makes it pointless, often with very few claims.
-
Survey completion is only 28.0% and is not size-representative; use population-weighting for population estimates, not raw percentages.
460/1,640 = 28.0%; survey size mix = 36.5% small, 39.6% 10-49, 23.9% 50-249 vs population 55% small, 35% 10-49, 10% 50-249. This understates small-firm weighting in raw tables.
Caveats
- 460/1,640 completes = 28.0%; the complete mix is skewed away from small firms (36.5% small vs 55% population) and toward 50-249 (23.9% vs 10% population), so population estimates use company-size weighting.
- Open-text answers are 109/460 (~24%), so theme lists are illustrative and not a representative subsample; 1-9 employee open answers over-represent small firms relative to population.
- Q3 is select-all with >100% totals; Q2 is a single-choice main-reason measure and can be self-mislabelled when one blocker is really another (e.g. required custom approval can look like setup).
- Likelihood to pay (Q5) is stated intent at a £6/user/month price, not observed conversion and not accounting for actual user counts, discounting, promo acceptance or ARPU.
- Population includes no 250+ employee trials; 250+ employee trends are unknown.
- Open-text headcounts occasionally disagree with the segment in the respondent ID (e.g. small ID with 8/10/12/15/18/25/30/35 people); segment is kept but text is used only for meaning.
- No 250+ employees, and 1-9 employees are only 36.5% of completes, so weighted estimates for the largest-population segment have more uncertainty.
Next steps
- decisionCommit next-quarter build to Sage integration (Sage Business Cloud/Sage Accounting/Sage 50/Sage 200); assess FreeAgent scope in parallel but do not delay Sage.
- experimentPilot assisted onboarding for 1-49 employee lapsed trials, with guided setup, checklist and named setup support.
- experimentRun a flat-rate/per-company pricing or capped-seat pilot for firms with many occasional users; keep per-user as baseline.
- researchRe-run/cohort follow-up after the Sage pilot and assisted-setup pilot; validate stated likelihood against actual paid status.
- monitorKeep 30-day trial, add usage-triggered reminders, do not ship a blanket 14-day cut.
Open-text themes it coded
Missing accounting-software integration 22Setup time / setup complexity 24Receipt scanning / mobile reliability 10Price / per-seat cost 23Approval workflow / sign-off model mismatch 15No real need / low expense volume 12Chose/went with another tool 8
The survey it planned
4 screening questions and 10 questions, as the model wrote them.
-
Q1
Is your business based in the UK?
One answer- Yes
- No
Continues if Yes
-
Q2
In the last 90 days, has your team's Tallyroom trial ended without your team becoming a paying customer?
One answer- Yes
- No
Continues if Yes
-
Q3
Are you the admin of your Tallyroom team?
One answer- Yes
- No
Continues if Yes
-
Q4
How many people work at your company?
One answer- 1-9
- 10-49
- 50-249
- 250 or more
Continues if 1-9; 10-49; 50-249
-
Q5
Which of the following stopped or delayed your team becoming a paying customer? Select all that apply.
Any that apply- Price or cost concerns
- Setup was difficult or took too long
- Missing integrations or features
- Not convinced Tallyroom would provide enough value
- The trial ended before a decision was made
- Our team wasn't ready to pay
- Didn't fit how our team works
- Other
-
Q6
Which of these was the single most important reason your team did not pay?
One answer- Price or cost concerns
- Setup was difficult or took too long
- Missing integrations or features
- Not convinced Tallyroom would provide enough value
- The trial ended before a decision was made
- Our team wasn't ready to pay
- Didn't fit how our team works
- Other
-
Q7
Which integrations or features would have made it easier for your team to pay? Select all that apply.
Any that apply- Sage accounting
- FreeAgent or another accounting app
- Bank feeds or reconciliation
- Multi-currency support
- Better VAT handling
- Better reporting and analytics for managers
- Multi-level approval workflows
- A better mobile app
- Nothing was missing — we were not convinced of value
Judges: double-barrelledThe only no-missing-feature option combines two distinct claims: nothing was missing and the team was unconvinced of value. Teams for whom neither features nor value was the problem cannot answer accurately, steering responses toward missing features or insufficient value.
The option 'Nothing was missing — we were not convinced of value' joins two separate claims. A respondent who was missing nothing but left over price or setup has no accurate answer to pick.
-
Q8
How much work did it take for your team to get Tallyroom working?
One answer- Very little — everything worked
- Some — a few issues
- A lot — significant issues
- We couldn't get it working properly
Judges: assumptiveAssumes the team attempted setup. Eligible teams that never attempted to get Tallyroom working have no applicable answer.
Assumes the respondent actually attempted to get Tallyroom working.
-
Q9
Would dedicated setup help have made your team more likely to pay?
One answer- Yes — definitely
- Yes — maybe
- No
Judges: leadingThe response scale offers definite and tentative positive answers but only an unqualified negative answer, encouraging uncertain respondents toward 'Yes — maybe'.
The options are unbalanced: two 'Yes' choices against one 'No'. This pushes answers towards saying setup help would have worked.
-
Q10
At which point in the trial did you first start considering whether to pay?
One answer- In the first few days
- Around week 2
- Around week 3
- Near the end of the 30 days
- Only after the trial ended
Judges: assumptiveAssumes every team started considering whether to pay. There is no answer for teams that never considered paying.
Assumes the respondent actively considered paying at some point.
-
Q11
Thinking about the 30-day length of the trial, which of these is closest to the truth?
One answer- A shorter trial would have helped
- A longer trial would have helped
- No difference
- Not sure
-
Q12
What would have made you confident enough to pay? Select all that apply.
Any that apply- More proof of value
- A lower price
- Help setting up
- More time to evaluate
- More integrations
- Nothing would have changed my decision
-
Q13
Attention check: for this question, please select option 'B'.
One answer- A
- B
- C
-
Q14
Is there anything else you'd like to share about why your team did not pay?
Open text
Sample plan
Invitation pool: all UK teams whose 30-day free trial ended in the last 90 days without paying (~1,900 quarterly starters x 82% lapsed = ~1,550 lapsed teams), with the 250+ employee teams excluded by the Q4 screener. Email the admin of each eligible team from the product database, including trial-start date and a £10 voucher per complete. Target ~450 completes; at a 25-30% response rate that means inviting the full lapsed pool (~1,500), with per-band invitation volumes weighted so the 10-49 and 50-249 bands receive additional invites to reach roughly equal completes. Quotas: aim for ~150 completes per band (1-9 / 10-49 / 50-249). Precision flag: +/-6pp at 95% confidence per band requires ~267 completes per band (~800 total) in the worst case; at ~450 completes an even split (150 per band) yields ~ +/-8.0pp per band (+/-6.9pp at 200 per band), so the 6pp target CANNOT be met per band at ~450 completes. Flag this to stakeholders before fieldwork: either authorize ~800 completes, or accept +/-8pp and require that no band report is published as '+/-6pp' where the achieved CI is wider. Report achieved CI per band per headline metric. Invitations must not mention the trial-length debate; the survey is built and worded neutrally so results can inform, not pre-confirm, the shorter-trial option.