KaaS
Resources
Book a 30 minute fit call

Keep your KaaS setup current as agents change

The Care Plan is a monthly retainer for teams with KaaS solutions installed. Each month we update skills for new agent releases, fix rules that misfire, and commit every change to your repo.

Scope your Care Plan

Run by the founder, a former Head of Software Engineering.

your-repoCare Plan commits, newest first

Plan stopped. No more commits from us. Every file above stays in your repo and keeps working.

  1. Month 3
    • Updated.claude/skills/spec.mdNew agent release: spec skill rewritten for it, checks unchanged
    • Fixedrules/review.mdA review rule that flagged generated test files, narrowed
    • Keptguard/budgets.yamlTeam budgets checked against last month, no change needed
  2. Month 2
    • UpdatedCLAUDE.mdTwo new architecture decisions added as context
    • Fixedpulse/report.sqlLead time now excludes reverted changes
    • Keptspecs/template.mdReviewed with the product lead, still fits
  3. Month 1
    • Updatedcontext/sources.mdNew service added, owner named
    • Keptrules/review.mdSenior engineers re-agreed the rules

Why it stops working on its own

Nothing fails loudly. Skills and rules fall a little further behind each month.

  1. A new agent release changes how skills behave. Skills and rules written for last quarter start to misfire quietly.

  2. Your system changes and the context falls behind. The team adds a service, a decision, a new convention. The context the agents read stays where it was.

Care Plan: Each month we check every installed solution against both and commit what needs it to your repo.

Scope your Care Plan

What each month gives you

Three kinds of commit, each one reviewed by your team.

Skills keep working through each agent release.

An Updated commit rewrites the skill for the release and leaves its checks unchanged.

Rules that misfire get fixed.

    You know what was checked and left alone.

    your repo

      Every change is a commit you can read.

      Your skills and rules keep pace with every agent release,

      and everything installed keeps working the month you stop.

      How a month runs

      The same three steps every month, in your repo.

      1. Check each installed solution against the month's agent releases and your own changes.

      2. Commit what needs it, tagged Updated, Fixed or Kept.

      3. Review the commits like any pull request.

        The owners named at handover approve what touches their part.

      “You work with the person who does the work. No handoff, no juniors, no account manager.”
      Paramanantham HarrisonFounder, KaaS.team

      Former Head of Software Engineering14 years building production software

      Questions teams ask before they book

      What is the Care Plan?

      A monthly retainer where we keep your installed KaaS solutions current. Each month lands as commits in your repo, tagged Updated, Fixed or Kept.

      Who is this for?

      Teams with KaaS solutions installed from a sprint or the programme, where nobody has time to track every agent release, and who want changes as commits they can review.

      Who is this not for?

      Teams with nothing installed yet, who should start with a Quick Win Sprint, and teams that want us to take over feature work.

      What happens if we stop the Care Plan?

      Nothing breaks. Everything we installed is in your repo and your cloud, and it keeps working. You stop getting new commits from us.

      What counts as Updated, Fixed and Kept?

      Updated means changed for a new agent release or a new part of your system. Fixed means a rule or check that misfired was corrected. Kept means we checked it and it still fits.

      Do we need a sprint or the programme first?

      Yes. The Care Plan looks after solutions that are already installed, so it follows a Quick Win Sprint, a Transformation Sprint or Agentic SDLC Transformation.

      Who reviews the changes?

      Your team does, like any other pull request. The owners named at handover approve what touches their part.

      How is the Care Plan priced?

      You get a written quote after the fit call, based on what is installed.

      Every month says what changed, including nothing.

      If a month needs no change, the log says Kept and why. We do not pad a month to look busy, and the delivery baseline from your programme stays the measure.

      BaselineAt the end

      Review waitMoved
      ReworkMoved
      Cycle timeDid not help

      1. Fit check first. If we are the wrong team, we will say so on the call.

      2. Stop anytime. Everything installed keeps working.

      Bring us the bottleneck.

      A 30 minute call with the founder about where work is stuck.

      1. Spec
      2. Build
      3. Review
      4. Release
      Where work is stuck
      Spec, build, review or release: wherever changes wait longest.
      What exists today
      The AI tools your teams use and the rules around them, if any.
      What the next quarter needs
      The launch or deadline the work has to hit.
      1. 1

        Call

        We find where the work waits and whether we can help.

      2. 2

        Fixed scope

        You get a written scope and a fixed quote before anything starts.

      3. 3

        Kickoff

        Work starts with your product and engineering leads.

      If we're not the right fit, we'll say so.

      Pick a time

      Open the calendar and choose any free slot. You get an invite with a video link.

      Scope your Care Plan

      Rather write first? Send a note