How we work
Clear models. A trusted partner. Results.
Choose a managed service, a project or the people you need, and we take it from there: one contact, visible tickets, a clear split of ownership and a written summary every month.
Engagement models
Five ways to work with us.
Each one works on its own or alongside the others. We explain how each model works, then quote for what you need.
Managed service
Fix-on-fail support
A monthly service that keeps the platform stable. We watch it, fix what breaks and work to response times agreed up front.
A good fit when: The platform keeps breaking and nobody owns the fix.
How fix-on-fail worksManaged service
Development retainer
Senior development hours reserved every month, worked from a backlog you prioritise with us. Unused hours roll into a bank.
A good fit when: The platform needs to keep moving forward, month after month.
How the retainer worksManaged service
Flex hours
Extra hours bought in advance, on top of a retainer, and drawn on only in the months that need them.
A good fit when: Some months are much busier than others.
How flex hours workProject
Projects
A defined piece of work with a clear end: a warehouse or cloud migration, a BI migration, a platform build or a governed metrics layer.
A good fit when: You know what needs to change and want it delivered.
See project typesPeople
Expertise and people
A lead or architect, analytics engineers inside your team, or your analytics run for you. We choose, manage and cover the people.
A good fit when: Your team needs senior direction or more capacity, and hiring is too slow.
See expertise and people
Getting started
From first call to first month, in four steps.
- 01
Discovery call
A short conversation about your platform, your team and what’s getting in the way. If we aren’t the right fit, we’ll tell you.
- 02
Platform health check
We review the platform as it stands: pipelines, models, reporting, monitoring and documentation. You get a plain account of what’s solid, what’s at risk and what to fix first.
- 03
Proposal
A written proposal setting out the model or mix of models, the scope, how we’ll work together and a tailored quote. Nothing starts until you’ve agreed it.
- 04
Mobilise
We set up access and tickets, agree who owns what, learn how your platform fits together and plan the first month. Then the work starts.
Ways of working
Four habits, in every engagement.
One point of contact
A senior lead who knows your platform and answers for the service. You always know who to call.
Every request in a ticket
Incidents, requests and changes are logged as tickets you can see, so you can check progress without chasing anyone.
A clear split of ownership
Your team and ours each know what they own, written down before the work starts. Nothing falls between the two.
A written summary every month
What happened on the platform, what we fixed, what we built and where the hours went.
Who owns what
An example split between your engineering team and ours. We agree the real one with you, in writing, while we mobilise.
| Aspect | Your team | Gosai Data Services |
|---|---|---|
| Priorities | Your team: Set the business priorities and sign off the backlog | GDS: Turn them into a plan and deliver it |
| Access and security | Your team: Grant access and approve security changes | GDS: Work within it, with access limited to what the work needs |
| Source systems | Your team: Own the source systems and the suppliers behind them | GDS: Spot data issues early and raise them with the right owner |
| The platform | Your team: Own anything outside the agreed scope | GDS: Own the pipelines, models and reports inside it, including monitoring and fixes |
| Definitions | Your team: Decide what each business metric means | GDS: Build it once, document it and keep it governed |
Compared with in-house
Senior capacity without the hiring cycle.
Hiring your own team is a real option. Here’s how it compares with working with us.
| Aspect | In-house team | Gosai Data Services |
|---|---|---|
| Cost | In-house: Fixed headcount, plus hiring and management cost | GDS: A predictable monthly run-rate, flexible on top |
| Seniority | In-house: Unknown, and often needs upskilling | GDS: Lead expertise in architecture, engineering and BI |
| Flexibility | In-house: Underused outside peaks, with a risk of churn | GDS: Stable support plus flex capacity for peaks |
| Continuity | In-house: Progress relies on one person | GDS: A team with structured cover |
| Speed | In-house: 3–9 months to hire and onboard | GDS: Immediate |
FAQ
Common questions.
Which model should we start with?
It depends on what’s hurting. A fragile platform usually starts with fix-on-fail support, a long backlog suits a development retainer, and a defined change suits a project. The discovery call and health check are there to work that out with you.
Can we combine models?
Yes. They’re built to work together: fix-on-fail support with a retainer on top, flex hours for busy months, or a lead role alongside a managed service.
Do we have to change our tools?
No. We work on the platform and tools you already run, unless moving off them is the point of the project.
What do you need from us to get started?
Access to the platform, someone on your side who can make decisions, and time with the people who know how things work today.
Next step
Book a discovery call
A short call to talk through your platform, your team and what is getting in the way.