Customer Entry Point
A structured public experience through which customers could discover services and begin a request.
Field Service & Marketplace Case Study
Building the First Version of a Connected Property-Services Platform
Isoft designed and developed the first version of GetCharlie, establishing a digital foundation that connected customers, service requests and operational teams through one coordinated workflow.
Connectedcustomers, service requests and operational workflows
ClientGetCharlie
IndustryProperty & Field Services
EngagementFirst-Version Platform
OutcomeConnected Foundation
The situation
A growing service operation needed to move beyond disconnected coordination
Coordinating property-service requests involves customers, office teams and people completing work in the field. When information is spread across spreadsheets and separate communication channels, teams spend more time reconstructing job status and less time moving work forward.
GetCharlie needed the first version of a digital platform that could establish a more consistent route from customer demand to operational action.
The goal was to create a practical platform foundation—not simply a public website—capable of supporting customer interactions and the operational workflow behind each service request.
The initial platform requirements
- Give customers a clear digital route into the service workflow
- Capture service-request information consistently
- Help operational teams coordinate and manage incoming work
- Improve visibility between office activity and work completed in the field
- Provide a foundation that could be extended as the business evolved
The solution
A first-version platform designed around the complete service journey
Isoft translated the operating model into a connected application foundation, creating the core digital journey needed to bring customers, requests and service operations together.
Service Catalogue
Administrative control over services and sub-services offered through the platform.
Request Capture
Consistent capture of customer, service and location information for operational follow-up.
Trade Professional Management
A foundation for organising the service providers responsible for fulfilling customer demand.
Lead Visibility
A central administration view showing recent requests, assignment and current status.
Extensible Foundation
A first-version architecture designed to provide a starting point for future services and platform development.
The connected workflow
From service discovery to operational follow-up
Discover
The customer enters through a structured digital property-services experience.
Request
Service, customer and location information is captured consistently.
Review
The operational team sees the new request and its current status centrally.
Coordinate
The request can be assigned and progressed using shared operational context.
Delivered platform views
Real screens from the first-version application
These anonymised views show the administration workflows delivered for customer-request visibility and service configuration.
Designed for real operations
Connecting the customer experience to the work happening behind it
A services marketplace succeeds only when the public experience and the operational process work together. The first version therefore needed to support more than service presentation—it needed to create dependable hand-offs between people and stages of work.
This operational focus gave GetCharlie a practical platform foundation that could continue to evolve as its service offering and business requirements developed.
Delivery principles
- Design around the service journey rather than isolated screens
- Make essential job information available at the point of work
- Reduce dependence on spreadsheet-based coordination
- Keep the first release focused on usable operational foundations
- Leave room for continued platform development
Operational result
A connected digital foundation for property-service operations
The first version gave GetCharlie a central platform foundation for bringing customer demand, service requests and operational activity into a more connected workflow.
One workflowconnecting customer-facing activity with the operational process behind service delivery
Mobile accesssupporting field personnel with relevant job information away from the office
Room to evolvethrough a first-version foundation that could support subsequent platform development
This case study covers the first version of the GetCharlie application delivered by Isoft. The current GetCharlie platform may include subsequent enhancements or features developed after the original engagement. No unverified financial or time-saving figures have been assigned.
Why this approach worked
The platform began with the operating workflow
Journey Before Features
The work began with how a service request should move between customers, office teams and field personnel.
Connected Participants
The first version considered the people involved across both the customer experience and operational delivery.
Practical First Release
The platform established the essential foundation needed for the product and workflow to continue evolving.
Related capabilities
Explore the work behind this result
Is your service operation still being coordinated through spreadsheets?
Book an Operational Systems Review to identify where customers, office teams and field personnel need a more connected workflow.