How the current picture usually forms
Traded services rarely start as a single commercial operation. Individual service teams begin charging schools for support, each builds the tooling it needs at the time, and over a decade those local solutions become the system of record. The result is not incompetence — it is the natural outcome of many teams solving their own problem well.
The typical estate includes a catalogue in a design file or PDF, pricing in several spreadsheets, order forms in Word or a survey tool, decisions in shared mailboxes, contracts in a document library, customer contacts in personal address books, and charging instructions in yet another spreadsheet passed to finance.
What fragmentation actually costs
Duplicate effort
The same information is entered repeatedly: a school's details appear in the order form, the contract, the finance instruction and the service team's own list. Every duplicate is a maintenance obligation, and when one copy is updated and the others are not, the organisation quietly loses confidence in all of them.
Slow, contested reporting
When someone asks for total traded income by service, or uptake compared with last year, the answer requires assembly. Because assembly involves judgement — which spreadsheet is current, whether that cancellation was processed — different people produce different numbers, and the discussion shifts from decisions to reconciliation.
Invisible commercial risk
Fragmented data hides patterns. A service losing a handful of schools each year, a customer steadily reducing its spend, or a group of schools that never renewed after a service change are all visible in connected data and effectively invisible across separate files.
An inconsistent customer experience
Schools experience the fragmentation directly. Different forms for different services, different contacts, different formats, and no single place to see what they hold. For a school business manager, the council can feel like several unrelated suppliers rather than one.
Key-person dependency
Undocumented processes concentrate in individuals. Where one officer knows how the buyback spreadsheet works, absence or turnover becomes an operational risk that no service continuity plan quite captures.
What 'connected' means in practice
A connected operation is not simply one system instead of ten. It means a small number of shared records that everything else references:
- Organisations — every school, academy, trust and other customer, with their own attributes such as pupil numbers.
- Services and products — the structured catalogue of what is sold, at what level of granularity.
- Pricing rules — how each product is priced, rather than a list of pre-calculated totals.
- Orders and contracts — what was agreed, by whom, for what period, at what price.
- Transactions — what should be charged, ready for export to the council's finance system.
- Interactions — enquiries, support requests and commercial conversations tied to the customer record.
Once those records exist in one structure, the things that previously required assembly — renewal packs, progress reports, income analysis, customer views — become queries.
What to consider before modernising
- 1
Map the real process, not the documented one
Interview the people doing the work. The informal steps — the mailbox rule, the manual check before invoicing — usually exist because something else does not work, and they need to be designed for, not designed out silently.
- 2
Audit your data quality honestly
Customer records, pupil numbers, current contract positions and pricing rules are the foundation. Migration difficulty is almost always a function of data quality rather than technology.
- 3
Decide what stays
The council's finance system, identity provider and MIS integrations are usually fixed. A traded-services platform should fit alongside them rather than attempt to replace them.
- 4
Model the pricing properly
Per-pupil, banded, tiered, fixed, minimum-charge and discount arrangements all need to be expressible as rules. If pricing can only be represented as static numbers, you have moved the spreadsheet rather than replaced it.
- 5
Plan around the buyback calendar
There is a narrow window in the year where change is realistic. Aligning implementation with the cycle avoids running two processes simultaneously during the busiest period.
- 6
Define success measurably
Administrative time saved, response rate, renewal rate, reporting turnaround and reduction in billing corrections are all measurable. Agree them before you start.
Sequencing the change
Attempting to replace everything at once is rarely necessary. A common and lower-risk sequence is to establish the customer and catalogue foundation first, then bring the annual buyback cycle onto the platform, then contracts and entitlements, then finance export, then commercial reporting. Each stage delivers something useful and reduces the effort required by the next.
It is also worth being realistic about what does not change. Modernising the tooling does not resolve unclear service definitions, inconsistent pricing decisions or under-resourced delivery. It does, however, make those issues visible, which is usually the first step to addressing them.
Service Street is built around this connected model — organisations, services and products, pricing rules, orders, contracts, transactions and customer interactions in one structure — specifically so that council teams can operate and grow traded services rather than spend the year maintaining the records that describe them.
In summary
Spreadsheets are not the problem in themselves; disconnection is. The value of modernising comes less from any individual feature than from the fact that customer, catalogue, contract and financial information finally describe the same reality — which is what makes confident commercial decisions possible.