Revenue & Customer Engagement Evidence
Turnover by revenue stream with the percentage each stream carries, the customer registration records, and the platform usage statistics — with the charts and the screenshots that evidence each figure.
Every year on this screen is the financial year the Home Office asked about — 1 July 2023 to 30 June 2024, 1 July 2024 to 30 June 2025 and 1 July 2025 to 30 June 2026. Revenue is shown two ways and both are labelled on screen: the split supplied in the company’s own sheet, each year taking that year’s column, and the sales ledger held in the portal for those same three years, which reconciles to the totals the Home Office requires. The client numbers are those who paid into the company’s bank accounts during each year.
Revenue generated, by category
The four categories requested, each with its sterling amount for the three financial years and its percentage of revenue.
i. Platform access and subscriptions
£0.00
0.0% of revenue recognised across the three financial years
Year ended 30 June 2024£0.00 · 0.0%
Year ended 30 June 2025£0.00 · 0.0%
Year ended 30 June 2026£0.00 · 0.0%
ii. Background screening services
£0.00
0.0% of revenue recognised across the three financial years
Year ended 30 June 2024£0.00 · 0.0%
Year ended 30 June 2025£0.00 · 0.0%
Year ended 30 June 2026£0.00 · 0.0%
iii. Due diligence services
£0.00
0.0% of revenue recognised across the three financial years
Year ended 30 June 2024£0.00 · 0.0%
Year ended 30 June 2025£0.00 · 0.0%
Year ended 30 June 2026£0.00 · 0.0%
iv. Other sources
£0.00
0.0% of revenue recognised across the three financial years
Year ended 30 June 2024£0.00 · 0.0%
Year ended 30 June 2025£0.00 · 0.0%
Year ended 30 June 2026£0.00 · 0.0%
Division of revenue each year — the three years to 30 June 2026
The year’s total revenue divided across the service lines, then the supplied split by service line with its % row and the category each line rolls up into.
Total revenue divided each year — the three years to 30 June 2026 (£)
The year’s total revenue, being every invoice dated between 1 July and 30 June of that year, divided across the service lines in the proportions supplied in the company’s own sheet. Each amount is followed by its share of that year’s revenue.
| Service line | Y/E 30 Jun 2024 | Y/E 30 Jun 2025 | Y/E 30 Jun 2026 | 3-year total | Share of 3 years |
|---|---|---|---|---|---|
| Portal subscription | £00.0% | £00.0% | £00.0% | £0 | 0.0% |
| BGV | £00.0% | £00.0% | £00.0% | £0 | 0.0% |
| Due diligence | £00.0% | £00.0% | £00.0% | £0 | 0.0% |
| Site visit | £00.0% | £00.0% | £00.0% | £0 | 0.0% |
| Other | £00.0% | £00.0% | £00.0% | £0 | 0.0% |
| Total revenue | £0 | £0 | £0 | £0 | 100.0% |
| Clients who paid in the year | 9 | 17 | 20 | — | — |
Each financial year’s total revenue is the sales ledger held in the portal added up: every invoice dated between 1 July and 30 June in that year, on the sterling revenue recognised. Each year’s total is then divided across the service lines in the proportions of the company’s own sheet for that same year, so the amounts add back to that year’s revenue.
Every column of the sheet totals 100, so each year’s revenue is divided in the sheet’s own proportions and the amounts add back to that year’s revenue. Site visits and other income were not recorded for the year to 30 June 2025 and are nil in that column, so that year is divided between portal subscription, BGV and due diligence. The percentage beneath each amount is its share of the revenue divided that year.
Clients who paid in the year: the paying companies and individuals whose payments were received into the company’s Starling and Barclays bank accounts between 1 July and 30 June that year, as shown on the bank statements supplied — each payer counted once however many payments it made. Card-acquirer settlements are excluded because no customer is named against them. Payments taken through PayPal and withdrawn to the same bank accounts are additional to these and are listed on the PayPal to bank invoices sheet: six withdrawals were received in the three years (three in the year to 30 June 2024 and three in the year to 30 June 2025), and the statements supplied do not yet cover the year to 30 June 2026.
Revenue split by service line — the three years to 30 June 2026
Revenue split by service line as supplied in the company’s own sheet, each financial year taking that year’s column of the sheet, and the % row is that column total. The column for the year to 30 June 2025 is restated to 100: the due diligence share is reduced from 25 to 15 and the portal subscription share increased from 52 to 54 by the same amount. Site visits and other income were not recorded that year and are nil in that column. Below each figure is its share of that year’s revenue, computed on the column total.
Portal subscription includes Packages, which carries all list services like education, employment, ID, criminal, civil, PEP, media check, due diligence etc.
| Service line | Rolled up as | Y/E 30 Jun 2024 | Y/E 30 Jun 2025 | Y/E 30 Jun 2026 | 3-year total | Share of 3 years |
|---|---|---|---|---|---|---|
| Portal subscription | i. Platform access and subscriptions | 4848.0% | 5454.0% | 5555.0% | 157 | 52.3% |
| BGV | ii. Background screening services | 2424.0% | 3131.0% | 1616.0% | 71 | 23.7% |
| Due diligence | iii. Due diligence services | 2222.0% | 1515.0% | 1515.0% | 52 | 17.3% |
| Site visit | iv. Other sources | 44.0% | 00.0% | 1010.0% | 14 | 4.7% |
| Other | iv. Other sources | 22.0% | 00.0% | 44.0% | 6 | 2.0% |
| % | Column total, as supplied | 100 | 100 | 100 | 300 | 100.0% |
| Clients who paid in the year | Per the bank statements, each payer counted once | 9 | 17 | 20 | — | — |
Source: Company revenue sheet for the three years ended 30 June 2024, 2025 and 2026, supplied by the applicant. Site visits are field-based work and are reported within “iv. Other sources” alongside all other income.
Clients who paid in the year: the paying companies and individuals whose payments were received into the company’s Starling and Barclays bank accounts between 1 July and 30 June that year, as shown on the bank statements supplied — each payer counted once however many payments it made. Card-acquirer settlements are excluded because no customer is named against them. Payments taken through PayPal and withdrawn to the same bank accounts are additional to these and are listed on the PayPal to bank invoices sheet: six withdrawals were received in the three years (three in the year to 30 June 2024 and three in the year to 30 June 2025), and the statements supplied do not yet cover the year to 30 June 2026.
Statistic graphs — percentage of revenue and revenue by stream
Share of revenue per year, revenue recognised per stream per financial year, and the share of the latest full year.
Percentage of revenue by service line — the three years to 30 June 2026
Stacked share of the supplied split, one bar for each financial year from 1 July to 30 June. Every column totals 100: the year to 30 June 2025 is restated to 100, with due diligence reduced and portal subscription increased, site visits and other income being nil that year.
- Portal subscription
- BGV
- Due diligence
- Site visit
- Other
Revenue recognised by stream, per financial year
Sterling recognised on the sales ledger, grouped into the four requested categories.
- i. Platform access and subscriptions
- ii. Background screening services
- iii. Due diligence services
- iv. Other sources
Share of revenue — Year ended 30 June 2026
Percentage of revenue recognised in each of the four categories in the most recent full financial year.
- i. Platform access and subscriptions
- ii. Background screening services
- iii. Due diligence services
- iv. Other sources
i. Platform access and subscriptions0.0%
ii. Background screening services0.0%
iii. Due diligence services0.0%
iv. Other sources0.0%
Revenue recognised — sales ledger, three financial years
Invoice-level revenue by stream, the percentage share of each stream, and the reconciliation to the totals required.
Revenue recognised, by stream and financial year
Taken invoice by invoice from the sales ledger held in the portal. Each figure is the sterling revenue recognised for that stream; the percentage beneath it is that stream’s share of the year.
| Revenue stream | Year ended 30 June 2024 | Year ended 30 June 2025 | Year ended 30 June 2026 | 3-year total | % of revenue |
|---|---|---|---|---|---|
| i. Platform access and subscriptions | £0.000.0% | £0.000.0% | £0.000.0% | £0.00 | 0.0% |
| ii. Background screening services | £0.000.0% | £0.000.0% | £0.000.0% | £0.00 | 0.0% |
| iii. Due diligence services | £0.000.0% | £0.000.0% | £0.000.0% | £0.00 | 0.0% |
| iv. Other sources | £0.000.0% | £0.000.0% | £0.000.0% | £0.00 | 0.0% |
| Total revenue recognised | £0.00 | £0.00 | £0.00 | £0.00 | 100.0% |
| Total required to reconcile | £94,520.00 | £111,442.00 | £221,515.00 | £427,477.00 | — |
| Variance | £-94,520.00 | £-111,442.00 | £-221,515.00 | £-427,477.00 | — |
| Invoices in the ledger | 0 | 0 | 0 | 0 | — |
Each financial year is the year ended 30 June, matching the totals the Home Office requires. The entries loaded are the portal reconstruction produced from the company’s own customer records; any entries dated outside the three years are excluded from the table above.
Revenue and profit divided by service line — the three years to 30 June 2026
Turnover and profit for each year, as the detailed profit and loss accounts state them, divided across the service lines in the company’s own proportions.
Turnover divided each year — the three years to 30 June 2026 (£)
Each year’s turnover, as the detailed profit and loss account states it, divided across the service lines in the company’s own proportions. Each amount is followed by its share of that year’s turnover.
| Service line | Y/E 30 Jun 2024 | Y/E 30 Jun 2025 | Y/E 30 Jun 2026 | 3-year total |
|---|---|---|---|---|
| Portal subscription | £45,37048.0% | £60,17954.0% | £121,83355.0% | £227,382 |
| BGV | £22,68524.0% | £34,54731.0% | £35,44216.0% | £92,674 |
| Due diligence | £20,79422.0% | £16,71615.0% | £33,22715.0% | £70,738 |
| Site visit | £3,7814.0% | £00.0% | £22,15210.0% | £25,932 |
| Other | £1,8902.0% | £00.0% | £8,8614.0% | £10,751 |
| Total turnover — per the profit and loss account | £94,520 | £111,442 | £221,515 | £427,477 |
Turnover and profit for each year are taken from the detailed profit and loss accounts supplied by the company for the three years ended 30 June 2024, 2025 and 2026. Each year’s turnover, and each year’s profit, is divided across the service lines in the proportions on the company’s own revenue sheet for that same year, so the amounts add back to the figure on the profit and loss account. Amounts are shown to two decimal places and percentages to one decimal place, the rounding difference being carried on the largest line of that year.
Profit divided each year — the three years to 30 June 2026 (£)
Each year’s profit divided across the service lines in the same proportions. Each amount is followed by its share of that year’s profit.
| Service line | Y/E 30 Jun 2024 | Y/E 30 Jun 2025 | Y/E 30 Jun 2026 | 3-year total |
|---|---|---|---|---|
| Portal subscription | £1,19248.0% | £10,93254.0% | £71,20055.0% | £83,323 |
| BGV | £59624.0% | £6,27631.0% | £20,71316.0% | £27,584 |
| Due diligence | £54622.0% | £3,03715.0% | £19,41815.0% | £23,001 |
| Site visit | £994.0% | £00.0% | £12,94510.0% | £13,045 |
| Other | £502.0% | £00.0% | £5,1784.0% | £5,228 |
| Total profit — per the profit and loss account | £2,483 | £20,244 | £129,454 | £152,181 |
Profit is the profit on ordinary activities before taxation, as stated on each detailed profit and loss account. The company’s sheet column for the year to 30 June 2025 is restated to 100, the due diligence share reduced and the portal subscription share increased by the same amount, and site visits and other income were not recorded for that year. That year’s turnover and profit are divided on that column total, so each year’s percentages add to 100. Amounts are shown to two decimal places and percentages to one decimal place, the rounding difference being carried on the largest line of that year.
Customer registration records, with their portal logins
Every customer organisation in the portal register, then the logins recorded against those accounts — month by month, with the IP addresses each login came from and the visits captured live.
Registration records
0
One row per customer organisation
Active accounts
0
0 not marked active
Countries represented
0
From the country on each record
Portal users issued
0
Records carrying a portal user account
New in the last 12 months
0
By registration date
Logins / cases recorded
0 / 0
Held against these accounts
Customer registration records — 0 records
Every customer organisation held in the portal register, with the country, plan, registration date, the portal user account issued to it, and the logins and cases recorded against it.
| # | Customer organisation | Country | Plan | Registered | Portal user account | Logins | Cases | Status |
|---|
Portal user accounts issued
0
0 hold a recorded login
Login events recorded
0
across 0 months
Distinct IP addresses
0
From the IP address written on each login event
Maximum logins recorded
—
No logins recorded yet
Logins month by month, with the IP addresses seen
Every login event carries the customer account that signed in, the date and time the login took place, the IP address it came from and the time the customer spent signed in. Each login is counted here on the date written on the event itself; where an event holds no date of its own, the date the event was written into the portal is used, and the totals still add back to the number of login events held.
| Month | Logins | Accounts | IP addresses | Account with the most logins | Its logins | Sessions measured | Session length recorded | IP addresses seen |
|---|---|---|---|---|---|---|---|---|
| No login events are recorded in the portal yet. | ||||||||
Customer accounts and their recorded logins
One row per portal user account that holds a login. 0 of the 0 accounts issued hold a recorded login.
| Customer | Portal user account | Role | Logins recorded | Months signing in | Sessions measured | Session length recorded | IP addresses | Last login |
|---|---|---|---|---|---|---|---|---|
| No portal account holds a recorded login yet. | ||||||||
Visits recorded live, with the visitor’s own IP address
A visit to the portal link is recorded as it happens, with the visitor’s real IP address, resolved location, network, device and time on site, and the figures are taken from those records.
| Visit started | IP address | Location | Network | Device | Time on site |
|---|---|---|---|---|---|
| No live portal visits are recorded yet. | |||||
Platform usage statistics, month by month
Registration and activation, core usage, and long-term commitment, each figure with how it is recorded — then the monthly volumes behind them.
Registered customer accounts
0
0 new in the last 12 months
Activation rate
0%
0 of 0 portal accounts have a recorded login
Active portal users — last 30 days
0
0 in the last 24 hours · stickiness 0%
Portal logins — last 30 days
0
0 logins recorded in total
Platform usage statistics
Every figure is an extract from the portal’s own records at 2026-10-29, with the screen each one is taken from. Where the platform does not record a measure, that is stated rather than estimated.
| Metric | Figure | How it is recorded | Source in the portal |
|---|---|---|---|
| Registration and activation | |||
| Registered customer accounts | 0 | One row per customer organisation in the portal register | Customer register — E-1.1 |
| Registered customer accounts with active status | 0 | Accounts whose status is recorded as active | Customer register — E-1.1 |
| New customer accounts in the last 12 months | 0 | Accounts created in the 12 months to the extraction date | Customer register — E-1.1 |
| Customer portal user accounts issued | 0 | Portal user accounts issued to customers, one or more per customer organisation | Client Portal Manager — E-1.2 |
| Activation rate — accounts with a recorded login | 0% | 0 of 0 portal accounts hold at least one login recorded | Client Portal Manager and activity log — E-1.2, E-1.3 |
| Time to first login (average) | Not measurable from the records held | Days from the account being created to the first login recorded for it, averaged over the 0 accounts whose first login falls in the login extract | Client Portal Manager and activity log — E-1.2, E-1.3 |
| Onboarding completion — accounts that have submitted a case | 0% | 0 customer accounts hold at least one case submitted through the portal | Customers & usage and case list — E-1.8, E-2.2 |
| Core usage | |||
| Portal logins recorded — last 24 hours | 0 | Login events written to the activity log in the last 24 hours | Activity log — E-1.3 |
| Portal logins recorded — last 7 days | 0 | Login events written to the activity log in the last 7 days | Activity log — E-1.3 |
| Portal logins recorded — last 30 days | 0 | Login events written to the activity log in the last 30 days | Activity log — E-1.3 |
| Portal logins recorded — cumulative | 0 | Every login event held in the activity log since the platform went live | Activity log — E-1.3 |
| Active portal users — last 24 hours (DAU) | 0 | Portal accounts whose most recent login falls within the last 24 hours | Client Portal Manager — E-1.2 |
| Active portal users — last 7 days (WAU) | 0 | Portal accounts whose most recent login falls within the last 7 days | Client Portal Manager — E-1.2 |
| Active portal users — last 30 days (MAU) | 0 | Portal accounts whose most recent login falls within the last 30 days | Client Portal Manager — E-1.2 |
| Platform stickiness (DAU ÷ MAU) | 0% | Daily active users divided by monthly active users, both measured from the recorded login history | Client Portal Manager and activity log — E-1.2, E-1.3 |
| Feature adoption — case submission | 0 of 0 users · 0 run | Customer accounts that have submitted at least one case, against the active user base | Case list — E-2.2 |
| Feature adoption — court record search | 5 of 0 users · 42 run | Portal users who have run a court record search, against the active user base | Search records and court search — E-1.4, E-2.5 |
| Feature adoption — credit check | 1 of 0 users · 2 run | Portal users who have run a credit check, against the active user base | Search records database — E-1.4 |
| Feature adoption — asset trace | 2 of 0 users · 11 run | Portal users who have run an asset trace, against the active user base | Search records and asset trace — E-1.4, E-2.9 |
| Platform volume — cases, subjects and searches | 0 cases · 0 subjects · 0 searches | 0 of the cases are recorded as completed; 19 instant searches are held in the log | Case list, subject register and search records — E-1.4, E-1.6, E-1.7, E-2.2 |
| Session duration (average time per visit) | Not recorded | No session times are recorded against the login events held | Activity log — E-1.3 |
| Longest single session recorded | — | No session times are recorded against the login events held | Activity log — E-1.3 |
| Loyalty and long-term commitment | |||
| Customer accounts held 12 months or more | 0 | Accounts whose registration date is 12 months or more before the extraction date | Customer register — E-1.1 |
| Average customer account tenure | — | Months from account registration to the extraction date, averaged across all accounts | Customer register — E-1.1 |
| Highest case volume held by a single customer account | 0 | Cases submitted by the highest-volume customer account held in the platform | Customers & usage — E-1.8 |
| Revenue recorded per customer account (average) | No sales ledger entries held in the portal | No allocated sales ledger entries are held in the portal for the period, so no figure is stated | Sales ledger and turnover evidence — E-1.8 |
| Milestone progression — accounts at 100 or more cases | 0 | Customer accounts that have passed 100 cases submitted through the platform | Customers & usage — E-1.8 |
| Net Promoter Score / customer satisfaction (NPS, CSAT) | Not collected | The platform does not issue a satisfaction survey, so no NPS or CSAT figure is recorded and none is stated here | — |
Months carrying activity
0
Every month with a registration, login or case
Portal logins in the period
0
Counted from the login events held in the portal
Busiest month for logins
—
No logins recorded yet
Cases submitted in the period
0
Case records in the portal
Platform usage, month by month
Customer registrations are counted by the registration date held on each registration record, portal logins by the date recorded on each login event, and cases submitted by the date the case record was created in the portal.
| Month | Customer registrations | Portal logins | Accounts signing in | Cases submitted | Avg session | Logins to date |
|---|---|---|---|---|---|---|
| No monthly activity is recorded in the portal yet. | ||||||
Monthly engagement, logins and cases, with the maximum logins
Customer registrations, portal logins and cases submitted month by month, then the maximum logins recorded — downloadable in Excel and in Word.
No monthly registration or login activity is recorded yet.
Busiest month for logins
—
Maximum logins, one account
—
Most logins by one account in a month
—
Most logins in one day
—
Maximum logins details
Each maximum is stated with how it is measured, so every figure can be traced back to the records it came from.
| Maximum | Value | How it is measured |
|---|---|---|
| Login events recorded | 0 | Every login event held in the portal activity log, counted one by one |
| Customer accounts with a login recorded | 0 | Of the 0 portal user accounts issued to customers |
| Months carrying login activity | 0 | No login events are held in the portal |
| Maximum logins recorded for one customer account | — | The highest login counter held against a single portal user account |
| Busiest month for logins | — | No login events are held in the portal |
| Maximum logins by one account in a month | — | The most logins a single customer account recorded within one month |
| Maximum logins in one day | — | The highest number of login events recorded on a single day |
| Session length recorded | — | No session times are recorded against the login events held |
| Average session length | — | The session times recorded added up and divided by the number of sessions measured |
| Days one account signed in more than once | 0 | Days on which the same customer account signed in two or more times, each sign-in counted separately |
| Distinct IP addresses in the login record | 0 | Each login event carries the IP address it came from; each address is counted once |
| Average logins per active account | 0 | Login events divided by the 0 accounts with a login recorded |
| Live-recorded visits and their locations | No live visits recorded yet | Each visit to the portal link is recorded as it happens with the real IP address and resolved location |
| Months shown in this table | 0 | Every month in which a registration, a login or a case is recorded |
Evidence screenshots
Captures each section of this screen exactly as it stands, with the figures and charts in it, so the evidence pack carries a picture of the screen the figures came from. Each capture is labelled with what it establishes, and the whole pack downloads as a Word document or a PDF with those labels and captions written in. The login records download with the pack as tables in the Word and PDF documents — the sign-in attempts month by month, the addresses each one came from and the session lengths — and on their own as an Excel workbook. The ZIP holds the Word pack, the PDF pack, the division of revenue workbook, the login records workbook and every screenshot.
1. Revenue by category and percentage
Shows the four revenue categories — platform access and subscriptions, background screening services, due diligence services and other sources — with the sterling revenue recognised in each of the three financial years and each one’s percentage of revenue. Establishes how turnover divides across the four streams the Home Office asked about.
2. Division of revenue each year — the three years to 30 June 2026
Shows each year’s total revenue divided across the service lines in the company’s own proportions, with the amount in sterling and its share of that year, then the company’s own revenue split by service line including its % row and the requested category each line rolls up into. Establishes the sterling division of revenue and the basis of the percentage split supplied.
3. Percentage of revenue charts
Shows the percentage of revenue carried by each service line in each year as a stacked share chart, the sterling revenue recognised by stream for each financial year, and the share of revenue in the most recent full year. Establishes the revenue mix and how it moved across the years.
4. Sales ledger by stream and financial year
Shows revenue recognised stream by stream for the years ended 30 June 2024, 2025 and 2026, the percentage share of each stream, the number of invoices behind each year, and the variance against the total required. Establishes that the turnover analysis reconciles to £94,520, £111,442 and £221,515.
5. Revenue and profit divided by service line — the three years to 30 June 2026
Shows the turnover and the profit on ordinary activities before taxation stated on each detailed profit and loss account for the three years ended 30 June 2024, 2025 and 2026, divided across the five service lines in the company’s own proportions, each amount followed by its share of that year. Establishes how the turnover and the profit divide across the service lines year by year.
6. Customer registration records, with their portal logins
Shows the customer registration records held in the portal, then the logins recorded against those accounts: the logins month by month with the IP addresses each login came from, the account with the most logins in each month, the logins held against each portal user account, and the visits recorded live with the visitor’s real IP address and resolved location. Establishes that registered customers sign in repeatedly each month, from the addresses recorded on each login, and that the visits are captured on the screen as a screenshot.
7. Platform usage statistics, month by month
Shows the platform usage statistics — registered accounts, activation, active users, logins, cases, subjects and searches — each with how it is recorded, then the month-by-month volumes: customer registrations, portal logins, accounts signing in, cases submitted and the running login total. Establishes the volume and frequency of customer usage of the platform.
8. Monthly engagement, logins and cases, with the maximum logins
Shows registrations, logins and cases submitted month by month, then the maximum logins details: the busiest month, the highest logins recorded for one customer account, the most logins by one account in a month, the busiest day, the distinct IP addresses and the average logins per active account, each with how it is measured. Establishes peak customer engagement on the platform. The same figures download in Excel and in Word.
