We use optional analytics to understand how this site is used and to improve it. You can allow it, decline it, or review the details first. Privacy policy
Managed Products · Ongoing care
After a Quick Win, a named Caritas steward can look after the product alongside your operator, handle covered issues, and show your executive sponsor how it is performing.
Your product stays yours. Your data is always yours. From handoff, you also own the code and infrastructure accounts, whether you operate it internally or choose ongoing care from Caritas.
What care looks like
A page can load while the work behind it has stopped. We run the checks and alerts named in your agreement, combine them with periodic manual checks, and give issues a person responsible for the next step.
Run the checks and alerts named in your agreement, such as whether the workflow ran and its inputs are fresh.
Use periodic manual checks to catch cases where a healthy status hides work that has stopped or gone wrong.
Triage incidents, make approved routine fixes and small approved changes up to a monthly hour cap, and apply patches your security owner approves.
Give your executive sponsor a clear account of your operating number, exceptions, and actions taken.
A continuing loop, with a named steward, backup, and agreed support channel.
For the executive sponsor
The monthly brief connects product health to the business workflow. It shows one operating number, exceptions, and the actions taken to keep the product useful.
We agree that number with you, with no guarantee of uptime or business results. Open risks and missing evidence stay visible, alongside decisions your team needs to make.
Illustrative product
Your team uses a custom application to turn approved source data into a recurring management report. Its monthly brief could show:
An example of the service structure, not a client result or a live report.
Scope and pricing
We price each product individually. The quote reflects its operating responsibilities, dependencies, required coverage, and maintenance scope.
One product may span several repositories and integrations. We start with the business capability your team relies on and agree its boundary together. Third-party fees are made explicit.
Agreed before coverage begins
Async triage and response are part of the fee. The one exception for live calls is a call to fix a break our own change caused.
Small approved changes fit within a monthly hour cap. New features, major integrations, and substantial rebuilding become separately scoped Quick Wins.
Discovery, strategic advice, and training outside the care agreement can continue through Groundwork.
How it fits together
01 / Groundwork
Start with a $1,000 activation. Live time and required compliance work are billed at accepted rates, prorated to the minute, under an agreed monthly cap. Supporting async discovery work is included while active.
Explore Groundwork02 / Quick Win in a Box
Agree a focused outcome, success criteria, and a separate value-based fee. Build and verify the result, with the delivery, training, and handoff your team needs to own it.
Explore Quick Wins03 / Delivery and signoff
At delivery, confirm who will operate and maintain the product. Your team can run it internally, or you can agree a Managed Products scope and coverage start date with us.
Your team operates
Your team takes ongoing responsibility after the agreed handoff. You keep the product and can maintain and extend it.
Caritas provides ongoing care
Your Caritas steward and backup take on the agreed care responsibilities from the coverage start date, working with your operator. You keep ownership and business direction.
The original delivery and handoff remain part of the Quick Win. Managed Products adds an agreed ongoing service after acceptance.
FAQ
Your data is always yours. From handoff, you also own the code and infrastructure accounts, whether your team operates the product or you choose Managed Products. Ongoing care is optional. The original Quick Win still includes its agreed delivery, training, and handoff obligations. A maintenance agreement does not replace those obligations.
A product is a defined business capability, such as a reporting workflow or an internal operations application. Its scope can include an application, scheduled jobs, and integrations across several repositories. We identify the covered environment and dependencies together before quoting. Each product receives its own fixed monthly quote.
The agreed scope includes a named Caritas steward and backup, the checks and alerts named in your agreement, periodic manual checks, approved routine bug fixes, patches your security owner approves, small approved changes up to a monthly hour cap, incident triage, and a monthly executive brief with one operating number. We do not guarantee uptime or business results. Service hours, response targets, maintenance boundaries, and any third-party fees are agreed before coverage begins.
We quote each product individually at a fixed monthly fee, based on its operating responsibilities, dependencies, required coverage, and maintenance scope. You approve the quote before coverage begins. Hosting, software subscriptions, usage charges, and other third-party fees are identified explicitly in the agreement.
We write down support hours, response targets, who to escalate to, and how we report against them. We also agree one operating number for your monthly brief, such as successful scheduled runs or fresh outputs. A response target is how quickly a person replies. We do not promise a repair time, and we do not control third-party services.
Async incident triage and response are part of the monthly fee. Live calls bill through Groundwork, except a call to fix a break our own change caused. Broader advice, discovery, and training outside the maintenance scope can also be handled through Groundwork. Small approved changes fit within a monthly hour cap. New features, major integrations, and substantial rebuilding are separately scoped Quick Wins. We agree the next step before additional work begins.
Coverage begins on the acceptance and start date agreed for the product. We first confirm the covered system, responsible people, access, operating baseline, response targets, and maintenance scope. Delivery issues and handoff work owed under the original Quick Win remain part of that engagement.
The agreement sets the notice period and transition responsibilities. We hand over the current operating documentation, access arrangements, the checks and alerts in place, and open issues to your designated owner or provider. Your company keeps its code, infrastructure accounts, and data. Any transition work beyond the agreed handover is scoped and approved separately.
The next conversation
Tell us which product your team relies on and the responsibility you want to share. We will confirm fit and what is needed to quote its care.
Email hello@caritas.ventures about your product.
