Your practice.
Working together.
Applications built around your practice: clearer oversight for partners, easier handovers for the team, and reporting connected to the work behind it.
We design new applications and improve existing systems for the way your firm works. That could mean a shared internal workspace, a focused tool for one process, or a better connection between the systems you already use.
For partners, practice managers and accounting teams. Start with the work that needs to become easier to see, share or manage.
Everyone is busy.
The picture is scattered.
Client work can spread across spreadsheets, shared folders, inboxes and specialist packages. Your people know how to join it together, but getting a clear view can take time and extra conversations.
Partners need the wider picture.
What is moving, what is waiting, who owns the next step and where deadlines need attention. Useful oversight starts with reliable information about the work.
Colleagues need the context to step in.
When someone is away or a job changes hands, the next person needs more than a status label. They need the relevant notes, correspondence, records and outstanding tasks.
Reporting needs a connection to the detail.
A management summary is more useful when people can understand the jobs, records and decisions behind it. We plan the information flow as part of the application.
Different perspectives.
Connected work.
One accountancy practice had been working across spreadsheets, shared drives and mail folders. It wanted clearer oversight for partners and an easier way for accountants to pick up one another’s jobs.
We have taken the project from requirements gathering through architecture and development, and into testing. Client Workbench brings client work, correspondence and reporting into a connected workspace.
A view across the practice.
The context for the next job.
Anonymised project screens from Client Workbench. The application is currently in testing with the practice.
Explore the full Client Workbench case study →A new application.
Or a better connection.
You do not need to arrive with a technology choice or an existing system to replace. We start with the work and agree what a useful first version should do. Desktop, web and mobile options are considered around who needs access and where the work happens.
A shared practice workspace.
A new application for job progress, responsibilities, handovers, requests and the information your team needs to act on. Views and permissions are designed around the people using it.
Partner oversight · Team coordination · Job context
A focused tool or connection.
Support a particular workflow, reporting requirement or exchange of information. We check available APIs, exports and access before agreeing how different systems can work together.
Requests · Reporting · Connections between tools
A future for an existing system.
Move beyond a spreadsheet process, improve an older database or plan a replacement for an application that has become difficult to maintain. Preserve the rules and records that matter.
Excel · Access · Older internal applications
Your existing specialist packages may remain part of the solution. We agree which work belongs in the new application and which connections are feasible before development begins.
Start with one workflow.
Build a useful foundation.
We can begin with a focused part of the practice rather than a whole-system change. The first phase needs a clear purpose, a way to check the result and an agreed place in the wider process.
See our full project process →
A useful starting question: where does a partner, manager or accountant have to chase information before they can move the work forward?
Understand the people and the work.
Explore the tasks, responsibilities, exceptions and information involved. Identify which systems and records the application needs to support.
Agree the first version.
Define the workflow, views, access levels and reports. Agree scope, price and timing, including any integration or data work that needs investigation.
Build and test with your team.
Review working progress using representative tasks and suitable example data. Check how work moves between people as well as how individual screens behave.
Plan a workable rollout.
Agree deployment, access, data checks, training and handover. Discuss support, maintenance and future phases as part of the project.
A few useful
answers.
Start with the work you want to support. We can help work through the technical details.
Can you build a completely new application for our practice?
Yes. A project can start with a new business requirement, a workflow that needs a shared tool or an idea for a different way of working. We help define the first version and design the application around its users and information.
Do we need to replace our existing accountancy software?
Not necessarily. We look at the role of your existing packages and agree what the new application should support. In some projects, a focused internal tool or a connection between systems may be the right first step.
Can you connect to the tools we already use?
We assess the available APIs, exports, permissions and technical dependencies before agreeing an integration. We do not assume that every package provides the access needed. The proposed approach and responsibilities are discussed before development starts.
Can partners and accountants have different views?
Yes. Roles, permissions and the information each person needs are part of the design. That can include an overview for partners, job context for accountants and appropriate access for other members of the practice.
Can you bring over records from spreadsheets or databases?
Often, yes. We check how the information is stored, what can be exported and how the records relate to one another. We agree data mapping, test imports and checks against the original information before changeover.
Is Client Workbench a product we can buy?
Client Workbench is a bespoke application for an individual practice and is currently in testing. It is shown as an example of our design and development work. For your firm, we would agree your requirements, scope and delivery approach separately.
What does a bespoke application cost?
The cost depends on the workflows, users, reporting, integrations and data involved. We agree the scope and price of the project or phase before the work begins. See our current project price guidance.
A clearer way to work.
Built around your firm.
Tell us where work gets difficult to see, share or hand over. Whether you have a new application in mind or an existing process that needs attention, we can help identify a practical next step.
A few sentences about your team, the work and what needs to become easier are enough to start.