Explain the recurring growth
Separate new business, expansion, contraction, reactivation and ended service. Use supported recurring service history to understand MRR, ARR and retention cohorts, with invoice evidence available for review.
PROFITCURA REVENUE INTELLIGENCE
Bring growth, customer pricing and delivery costs into the same monthly review. Profitcura Revenue Intelligence helps small software, hosting and managed IT businesses get more useful answers from their existing billing exports.
Keep your billing tools. Start with an export. Add the detail your next question needs.
THE MARGIN BEHIND THE PLAN
| Plan | Net billed | Direct cost | Margin |
|---|---|---|---|
| Cloud seats40 seats · monthly | £1,044.00 | £280.00 | 73.18% |
| Team software25 seats · monthly | £1,975.00 | £600.00 | 69.62% |
| Managed IT20 seats · monthly | £2,384.00 | £2,240.00 | 6.04% |
Review Managed IT: a 20% discount leaves only a 6.04% direct margin at the supplied costs.
A MORE USEFUL MONTHLY REVIEW
Separate new business, expansion, contraction, reactivation and ended service. Use supported recurring service history to understand MRR, ARR and retention cohorts, with invoice evidence available for review.
Compare customers buying matching products, units and service terms. See observed discounts against supplied list prices, then check contract and volume context before calling a difference an opportunity.
Bring supplied direct costs or dated unit-cost references into the review. Identify plans where licence, infrastructure or support costs leave a thin direct margin, and make missing or estimated costs visible.
FROM BILLING EVIDENCE TO THE NEXT ACTION
Bring the recurring base, customer prices and covered delivery costs into one discussion. Keep the source and calculation basis visible as you move between views.
See the product modulesAn IT provider may sell a software plan, cloud capacity and a support package on the same invoice. Classifying the recurring lines and their service periods lets you follow the subscription base without treating setup fees or irregular charges as MRR.
Review which customers drive expansion and which cohorts lose recurring value. A service term ending in the imported history is a question to investigate: check whether the renewal export is complete before treating it as a confirmed cancellation.
A lower billed unit price can reflect an introductory offer, committed volume, a different entitlement or a legacy agreement. Compare like-for-like plans and billing terms, then validate the contract. An observed discount is not proof of unauthorised leakage or automatically recoverable revenue.
Profitcura connects measured pricing findings to a scenario. Test a price increase, discount reduction or cost change, and state how much billable volume you assume will remain. Save the test so a later commercial review can revisit the same evidence and assumptions.
Add a small acquisition-cost upload to review cohort CAC, observed customer value to date and gross-profit payback when matching service and cost history is available. Keep the original acquired-customer denominator so customers who leave do not disappear from the acquisition calculation.
Benchmarks and targets are references supplied by your team, with source and date context. Optional AI explanations help interpret verified aggregate findings; history-based billing forecasts show their observation window and error measures. A price scenario is an assumption-based test, not a learned prediction of customer demand.
AN EXAMPLE, WITH THE ASSUMPTIONS INCLUDED
Consider the fictional Managed IT plan above: 20 monthly seats billed at £119.20 each, against a £149.00 list price and £112.00 direct cost per seat. Compare the recorded position with one explicitly assumed price test.
Before recommending the change, check renewal dates, price commitments, the customer's seat entitlement and whether the supplied direct costs cover the service being delivered.
Fictional monthly example · GBP · tax excluded
| Monthly result | Recorded | Illustrative test |
|---|---|---|
| Net billings | £2,384.00 | £2,491.28 |
| Direct costs | £2,240.00 | £2,128.00 |
| Direct gross profit | £144.00 | £363.28 |
| Direct margin | 6.04% | 14.58% |
AssumptionsIllustrative test: billed unit price +10%, with 95% of billable volume retained (19 seats). Direct unit cost stays £112.00 and varies fully with volume. All seats in scope are repriced; no tax or overheads are included.
This is an assumed commercial test, not a customer result, forecast or guaranteed uplift.
Explore saved pricing scenariosSMALL INPUTS. CLEAR DATA BOUNDARIES.
A four-column file starts invoice-based analysis. Add the fields that support the next question, with missing coverage visible throughout the review.
For IT providers, product IDs should distinguish matching plans and billed units. Keep monthly and annual variants clear, and supply the service period rather than inferring it from the invoice date. Variable usage charges stay separate from fixed recurring commitments.
KNOW THE METRIC BEHIND THE CONVERSATION
Normalise subscriptions, explain movements and separate MRR from invoices and cash.
Read the guide ARRUnderstand the annualised run rate, contract value and a reliable ARR bridge.
Read the guide ChurnCalculate customer churn, gross revenue churn, net churn, GRR and NRR.
Read the guide CohortsRead retention tables, compare equal customer ages and investigate patterns.
Read the guideBEFORE YOUR FIRST REVIEW
Both can use a billing-data-led review where the export identifies customers, recurring products and covered service periods. For managed IT or hosting, supplied delivery costs are important for direct-margin analysis. The product does not replace a PSA, ticketing platform, vendor procurement system or billing engine.
Start with a CSV export, map the columns and review the validation. Keep invoicing and collecting payments in your current system. Native live billing or PSA connectors are not currently offered.
Four columns—invoice ID, date, customer ID and net amount—support invoice-based analysis. MRR needs supported recurring classification and service dates. Product pricing needs product IDs and quantities; discounts need list prices or explicit discount detail, and margins need direct costs.
Current pricing scenarios calculate outcomes from assumptions you enter, including retained billable volume. They do not infer price elasticity or prove a causal effect. Optional AI commentary explains measured findings and suggests review steps; it does not change customer prices.
Request a walkthrough of Profitcura Revenue Intelligence. The product is in active development, with pilot access and commercial terms agreed separately. The industry example on this page is fictional and is not a customer result or market benchmark.
YOUR NEXT REVIEW CAN START HERE
Explore Profitcura Revenue Intelligence in a walkthrough focused on your business. The product is in active development; pilot access and terms are agreed separately.