Background
Cyberland builds B2B2C CRM platforms for SMBs. Our core market — and the business we were built on — is early childhood education: preschools and kindergartens serving children aged 0–6. The platform helps these centres manage enrolments, track child development activities, coordinate staff, and communicate with parents.
For years, this was a strong, defensible position. But the structural tailwinds that had driven growth were reversing:
- Singapore's TFR fell from 1.10 in 2020 to 0.97 in 2024 — well below the replacement level of 2.1 and among the lowest in the world
- Live resident births dropped from 35,129 in 2010 to approximately 33,700 in 2024
- Fewer births meant fewer children entering the preschool system and fewer new centres opening
The number of preschool centres in Singapore had effectively plateaued — our core market was saturated.
The ceiling was structural, not cyclical — we were competing harder for a market that was no longer expanding. Deeper penetration wasn't going to fix it. We needed to find a new vertical before the core business started contracting.
I was given end-to-end ownership of that problem: identify the right vertical, validate the opportunity, define the product, and bring it to market. No playbook existed. The call was mine to make.
The Strategic Question
Our mission has always been to be the best implementation partner for our clients — not just to sell software, but to understand their operations deeply enough that our platform genuinely moves their business forward. That standard ruled out any vertical where we'd be starting from zero.
The real question was: where can we walk in as practitioners, apply what we've already built, and create immediate, compounding value for a new client base?
To answer that, I defined three criteria that any candidate vertical had to meet before it was worth evaluating seriously.
Domain knowledge transfer. We weren't a big company that could afford to learn a new industry on the job. The vertical had to be one where our existing knowledge of care-based operations gave us a running start — not a blank page.
Platform reusability. We had a working CRM. The vertical had to be close enough to our existing use cases that we could configure our way in, not engineer our way in. Every month spent building net-new features was a month we weren't generating revenue.
Brand transferability. Cold trust is expensive to build. We needed a vertical where the relationships and reputation we'd built in early childhood education could open the first doors — so we weren't starting every conversation from zero.
With these criteria defined, I conducted a market analysis across the verticals we could potentially tap into.
Market Analysis
I mapped five candidate verticals against the three criteria from my strategic framework, adding revenue potential and competitive density as two additional dimensions to separate verticals that passed the fit test but differed on commercial and timing factors.
| Vertical | Domain Knowledge Transfer | Platform Reusability | Brand Transferability | Revenue Potential | Competition |
|---|---|---|---|---|---|
| Aged Care | Medium | Medium | Low | High | Low |
| International Schools | Low | Low | Medium | High | High |
| Children & Youth Services | High | High | High | High | Low |
| Student Care | High | High | High | Medium | Medium |
| Tuition Centres | Medium | Medium | Low | Medium | High |
International Schools and Tuition Centres were eliminated early — both failed on platform reusability and competitive density. Aged Care scored well on revenue and competition but the workflow match wasn't strong enough to clear our configuration constraints. That left two serious contenders: Student Care and Children & Youth Services.
Both scored identically on domain knowledge, platform reusability, and brand transferability. The final question was timing — which vertical had the right conditions to enter right now. 3 market trends pointed clearly to Children & Youth Services.
- Digitisation mandate. Government funders were actively pushing Children & Youth Services organisations away from paper-based processes. Compliance reporting requirements were growing faster than spreadsheets could absorb.
- Active procurement budgets. Government-affiliated bodies had digitisation budgets and were actively seeking vendors. The willingness to pay existed — the right product just hadn't shown up yet.
- Greenfield market. The CRM tools these organisations were using were free — nonprofit arms of larger vendors, provided as goodwill with no meaningful support or roadmap. Any changes required budget that either wasn't approved or didn't exist. The result was a sector stuck on tools that nobody was improving, with organisations that had no path to upgrade on their own.
With the vertical confirmed, I moved into discovery to pressure-test the assumptions before committing a single line of the PRD.
Discovery & Validation
I ran discovery interviews and mini design thinking workshops with six organisations across three care categories — children's homes, special needs schools, and early intervention centres. We got access through referrals from existing clients who were part of larger group organisations with networks across the sector.
Each session brought together operational staff and directors to co-create workflow diagrams and swim lane maps. This gave us a clear, ground-up picture of how work actually moved through their organisations and where it broke down.
Three problems surfaced consistently across every session without prompting.
Generic CRMs couldn't fit their needs.
Unlike education, where requirements are largely standardised, social service organisations each define their own approach to casework. Every client has a unique history, unique goals, and a unique intervention plan. No off-the-shelf tool was built for that variability.
No centralised record meant no shared visibility.
Staff were storing client information across personal Excel sheets and Word documents. In multi-department organisations, different teams working with the same client had no way to review that client holistically or coordinate the next intervention. Making data-enabled decisions about a client's care was difficult, incomplete, and operationally costly.
Audit season was dreaded.
Organisations had to pass compliance audits from MSF, NCSS, and their own funders regularly. With records scattered across individual files, consolidating everything from scratch was their most stressful operational period — staff routinely returned during public holidays just to get submissions ready.
These three problems were connected. Scattered records made case management unreliable. Unreliable case management made compliance reporting painful. One fix addressed all three.
Product Strategy
The Strategic Frame
The decision going into the PRD was vertical configuration, not a ground-up rebuild. Our engineering team estimated that 70% of what Children & Youth Services organisations needed already existed in our platform. The build was an extension, not a reinvention. I wrote the PRD and presented it to our engineering leads and CEO for resourcing sign-off before development began.
Prioritisation
Two criteria drove every scoping decision: does it directly solve a problem surfaced in discovery, and can it be built without significant new engineering? Features that cleared both went into v1. Everything else was documented and deferred.
| Feature | Priority | Rationale |
|---|---|---|
| Enrollment | v1 | Entry point for every client record. Nothing else works without it. |
| Case Management Module | v1 | Centralises records across departments. Solves the core visibility problem. |
| Audit Trail | v1 | Timestamps every action. Directly addresses accountability and compliance gaps. |
| Report Generator | v1 | Built on clean centralised data. Turns audit prep from days into minutes. |
| Transport Management | Deferred | Operational need but not the reason organisations were switching platforms. |
| Billing | Deferred | Real requirement, low discovery priority. Queued for next phase. |
| Scheduling | Deferred | Coordination need identified in discovery but not universally critical across all organisation types. |
| Non-Essential Case Reports | Deferred | Edge-case compliance documents. Not universal across organisations. |
Build Sequence
The sequence wasn't arbitrary. Each module was only as useful as the one before it.
Enrollment feeds case management. Case management feeds the audit trail. The audit trail feeds the report generator.
That dependency chain determined the order — and made it non-negotiable.
Go-to-Market
Who we targeted and why
We focused on early intervention centres as our entry point into social services. The strategic logic was direct — these organisations serve children in the 0–6 age group, the same population our existing education platform was built around. That overlap made our referral network transferable from day one.
How we got in the room
New relationships came primarily through referrals from existing preschool and kindergarten clients. Social service organisations serving young children shared funding bodies, government relationships, and community networks with the centres we already worked with. Trust transferred. We didn't build credibility from zero — we borrowed it.
The sales sequence
- Operations first. Every engagement started with caseworkers. Discovery told us they were spending 20–30% of their time on manual compliance reporting. Every demo led with that — a concrete before-and-after for their working week.
- IT and leadership second. Only after the operations team was convinced did we bring in IT and leadership together for compliance and requirements review: security architecture, PDPA alignment, and data governance.
This sequence was deliberate. Caseworker buy-in gave leadership and IT a demand signal to respond to — not a cold pitch to evaluate.
Onboarding and adoption
- UAT before go-live. Key stakeholders tested the customised build and resolved gaps before any end user touched the platform.
- Department-specific training. Each team was trained on their own modules and workflows — not a single mass session.
- Train-the-trainer. Internal champions were identified in each department and equipped to support their colleagues independently.
- Phased rollout. Core operations teams went live first. Remaining modules followed once the foundation was stable.
- Three-month intensive support. Change management risk peaks immediately after launch. We stayed close during that window to catch issues before they became habits.
How we measured success
Renewal rate, satisfaction scores, and time saved on compliance reporting — all of which trace back to one thing: whether caseworkers genuinely integrated the platform into their daily work. Getting the contract signed was the entry. Keeping caseworkers using it was the win.
Impact
Commercial
- Generated $1M in new revenue from an initial cohort of two anchor organisations
- Both clients renewed and expanded into adjacent services including special needs schools and other social service units
Credibility and Market Position
- Both anchor organisations were recognised names in Singapore's youth and social service sector
- Their early adoption established Cyberland as a credible vendor in a referral-driven market, directly unlocking the pipeline that made the $1M target achievable
Product and Operational
- Post-rollout survey showed caseworkers saved an average of one hour per day previously lost to manual compliance reporting
- Customer satisfaction averaged 4–5 stars across the first cohort, validating both product quality and the structured onboarding process
Strategic
- 70% platform reuse meant Cyberland entered a new vertical without a ground-up rebuild, preserving margin while proving the core CRM architecture was transferable across adjacent sectors
What I'd Do Differently
Change management takes longer than the product does
- Mistake: Underestimated the inertia of non-tech-savvy users shifting to a new system. A single training session at go-live wasn't enough to drive independent adoption.
- Lesson: Build sustained, repeated training into the post-launch phase from day one — not just availability, but structured sessions until users operate without supervision.
Security reviews, tender submissions, and compliance checks extend the sales cycle significantly
- Mistake: Didn't fully account for the cumulative time that procurement, tender submissions, security reviews, and compliance checks add in government-adjacent sectors. This created budget and resourcing strain mid-cycle.
- Lesson: Plan team capacity and runway around the full sales cycle, not the product timeline. In regulated sectors, every procurement gate compounds — assume the deal takes twice as long as expected.
UAT doesn't replace real-world validation
- Mistake: UAT and sign-off caught what users knew to test for — but edge cases only surfaced once the platform was live at scale across 50–300 caseworkers.
- Lesson: Run a structured 30-day parallel trial alongside the existing system before full go-live. Real daily use surfaces what controlled testing never will — and makes the eventual launch far cleaner.