PRICING
Understand the cost before you commit.
Projects are quoted individually. Tell me what is taking too much time; I’ll explain the work, service fees, software costs, and any ongoing support before you decide.
DEMONSTRATION · SAMPLE DATA
Illustrative proposal · Sample content
Ways to work together.
Work out where to start
When you need a clear starting point.
Review your process, existing systems, and priorities to define a practical way forward.
- Process and requirements review
- Options and feasibility
- Recommended scope and next steps
Deliverables and fee agreed in advance.
Discuss assessment & planning →Improve one process
When the outcome is well defined.
Build an application, workflow, dashboard, portal, assistant, or integration around agreed requirements.
- Written scope and milestones
- Development and testing
- Agreed handover and training
Proposal based on the agreed scope.
Discuss scoped project →Connect several parts of your business
When several systems or workstreams need to come together.
Plan and deliver connected changes through agreed phases and review points.
- Phased delivery plan
- Dependencies and specialist input
- Reviews and change handling
Phases, responsibilities, and fees set out in writing.
Discuss larger implementation →Ongoing managed support
When you need help after launch.
Keep the systems you rely on working as your needs change. Support can include agreed monitoring, troubleshooting, maintenance, and improvements. Coverage, response expectations, and fees are set out in your agreement.
- Defined support coverage
- Maintenance and troubleshooting
- Agreed improvement work
Coverage, response expectations, and fees agreed.
Discuss ongoing support →Service fees and software costs are separate.
Solvency Studio service fees
- Assessment and planning
- Design, development, and testing
- Agreed training and support
Software and operating costs
- Microsoft and other platform licenses
- Usage, capacity, and hosting
- Third-party tools and services
Your proposal identifies the expected costs, who provides each service, and who pays each provider.
What shapes your proposal?
How many steps are involved
Steps, decisions, and exceptions.
Which tools need to connect
Connections and dependencies.
How much information needs organizing
Source quality and structure.
Who needs to see or change information
Users and audiences.
Training & handover
Documentation and practical guidance.
The help you need after launch
Coverage and future improvements.
Specialist input and delivery dependencies are included where the project requires them.
Agree the work before it begins.
01
Understand the need
Discuss goals, priorities, and existing tools.
02
Review the proposal
Confirm deliverables, costs, responsibilities, and milestones.
03
Approve the scope
Agree the work in writing before delivery starts.
If the scope changes.
We explain the impact on cost and timing, then agree the update before additional work begins.
Let’s define the right next step.
Tell us what you want to achieve. We’ll help shape a suitable engagement.
