The need
Give distributed customer teams a consistent communications layer.
← Ventures & experience
Historical venture
PearCall
Software created because the operating model needed it.
OLSEN STEINER ROLE · VENTURE DEVELOPMENT · OPERATING TECHNOLOGYConnect → Route → Support
200+Operator-scale environment
3Call-centre locations
RegionalDistributed teams
Internal leveragePrimary economic role
Historical operating experience, not a current holding. No public exit or realised-return figure is claimed.
THE CASE IN ONE VIEW
The need. The model.
The role we play.
The model
Telephony, agent workflows and operational reporting.
Our role
Proprietary software development for regional operations.
HOW THE MODEL CONNECTS
From one step
to the next.
01Route→
02Work→
03Control→
04Report→
05Improve
FULL CONTEXT
The complete background, on demand.
The visual overview is the short route. Open a chapter to read the original explanation and supporting detail.
PearCall
OPERATING TRACK RECORD CASE
HISTORICAL VENTURE · COMMUNICATIONS TECHNOLOGY
OLSEN STEINER ROLE · VENTURE DEVELOPMENT · OPERATING TECHNOLOGYPearCall
Software created because the operating model needed it.
200+Operator-scale environment
3Call-centre locations
RegionalDistributed teams
Internal leveragePrimary economic role
CASE EXPLORER
The detail, when you need it.
Open a chapter for the operating evidence, economics, partners or development assumptions. All financial qualifications and source links remain with their context.
INVESTMENT / OPERATING THESISBuild the system when generic software becomes the bottleneck.+
INVESTMENT / OPERATING THESIS
Build the system when generic software becomes the bottleneck.
PearCall was not conceived as software looking for a problem. It emerged from the requirements of distributed customer operations at scale.
Workflow before feature list
The product was shaped around real agent and supervisor workflows.
Visibility creates control
Operational reporting matters when teams, locations and markets multiply.
Infrastructure can be strategic
Internal software can create operating leverage even when it is not the principal revenue line.
MARKET FOOTPRINTTechnology supporting a regional operating footprint.+
MARKET FOOTPRINT
Technology supporting a regional operating footprint.
PearCall supported customer operations associated with the wider SojiLabs / CPA IKON ecosystem.
VietnamCore operating environment
IndonesiaRegional customer operations
PhilippinesRegional customer operations
MalaysiaServed through regional operations
The footprint reflects the operating environment the platform supported, not standalone PearCall sales territories.
BUSINESS MODELA communications layer around the agent workflow.+
BUSINESS MODEL
A communications layer around the agent workflow.
The economic value came from connecting telephony, people and management information.
01Route
Calls and leads reach the right workflow.
02Work
Agents handle customer conversations.
03Control
Supervisors monitor activity and quality.
04Report
Operational data supports management decisions.
05Improve
Workflows evolve around conversion and service needs.
COMMERCIAL / FINANCIAL LENSAn internal operating-leverage asset.+
COMMERCIAL / FINANCIAL LENS
An internal operating-leverage asset.
PearCall’s strategic value was primarily operational rather than standalone SaaS revenue.
Revenue roleIndirect
Supported revenue-generating telesales and customer operations.
Cost leverTooling control
Reduced dependency on fragmented external systems.
Scale leverStandardised workflow
Made distributed operating processes easier to manage.
Capital intensityLow
Software development and implementation rather than physical infrastructure.
WHAT MADE IT HARDExecution risk, not presentation risk.+
WHAT MADE IT HARD
Execution risk, not presentation risk.
These cases are included because they required real operating decisions, not because every element was frictionless.
Internal tools fail if agents and supervisors work around them.
Telephony infrastructure has to work during revenue-critical activity.
Management information is only useful if workflows capture clean data.
Internal platforms must solve operating pain, not become technology vanity projects.
HISTORICAL VALUE CREATIONA technology asset created from an operating bottleneck.+
HISTORICAL VALUE CREATION
A technology asset created from an operating bottleneck.
PearCall demonstrates a different type of venture value: software did not need to be sold externally to be economically useful. It reduced dependency on generic tooling and supported distributed revenue-generating operations.
PROBLEMDistributed telesales
Multiple teams and locations created a need for workflow, telephony and management visibility.
BUILDPurpose-built software
The product was shaped around identifiable agent and supervisor workflows.
VALUEOperating leverage
Internal infrastructure supported scale and standardisation across a 200+ operator environment.
INVESTOR RELEVANCEBuild vs buy discipline
Evidence of building proprietary technology only where it materially improved the operating model.
OLSEN STEINER ROLETechnology developed from operating necessity.+
OLSEN STEINER ROLE
Technology developed from operating necessity.
Olsen Steiner’s role was to connect the software brief to the commercial reality of the businesses using it. PearCall is evidence of a recurring Olsen Steiner principle: build technology when it materially improves the operating system, not because software is fashionable.
Case detailExplore the detail+
Public outcome disclosure
PearCall is not presented as a standalone realised software exit. Its historical value was primarily embedded in the operating businesses it supported. No public standalone transaction value or realised-return figure is claimed.
THE NEXT CONVERSATION
A defined challenge.
A practical way forward.
Tell us the market, the opportunity and what needs to happen next.