Every project ends. That is the nature of a project: it has a scope, a timeline, and a close. When the website is finished it is handed over. When the CRM is configured and the contractor walks away, someone has to hold it. When the analytics dashboard is built and the engagement invoice is paid, the data has to be read, acted on, and updated. The project created an artifact. Something now has to hold that artifact.
This is the problem the standing partner model solves. Not the build. What comes after the build.
What Projects Actually Cost You
The visible cost of a project is the invoice. The invisible cost is the loss of context that happens at handover.
When a technology partner builds your website, they develop a detailed mental model of your business over the course of the engagement: your clients, your tone, your competitive position, the compromises that were made, the decisions that went a different direction. That mental model lives in the partner's head. When the project closes, it walks out with them.
The next time you need work done, you hire someone new. The briefing starts from scratch. The decisions that were carefully made last time are not visible to the new person, so they get remade, sometimes in conflict with what is already there. The work becomes inconsistent. The environment accumulates decisions made by different people in different periods with different understandings of your business.
Over three years of project-based engagements, a typical business has three to five technology contractors who have each worked in their own lane with partial context. The result is a technology environment that is technically functional but not coherent. It works, mostly, until it does not.
What Holding Actually Means
In the Yutie model, a business has eight domains: Presence, Reach, Relationships, Operations, Finance Visibility, Stewardship, Intelligence, and Readiness. Each domain has a state. A domain can be Tending (actively improving), Waiting (stable, not the current priority), or Quiet (underserved, needs attention). The Shalom Score is the composite measure of how all eight domains are doing at any given moment.
Holding an environment means knowing the state of all eight domains, month after month, and making the right interventions at the right time. It is not possible to hold an environment if you are not continuously present in it. A project team is not continuously present. They arrive, build, and leave. A standing partner is always there.
This is what retainers make possible. Not just the work that happens each month, but the continuity of context across months. A standing partner knows that the CRM was configured in March specifically to handle a particular sales motion the owner was running at the time. They know that the website copy was updated in January to reflect a pricing change. They know that the analytics dashboard was set up to track a cohort that turned out not to be the right cohort. They know where all the bodies are buried.
Why Serious Businesses Need This More Than Anyone
Small businesses can sometimes absorb the discontinuity of project work because their technology environment is simple enough that a new contractor can get up to speed quickly. A business with one website, one email account, and one WhatsApp number does not need a standing partner. The context load is low.
Serious businesses have complex environments. Multiple services talking to each other. A CRM with years of pipeline data. A website that has to serve different audiences with different intent. Finance systems that touch the CRM. Analytics that inform the website. A proposal workflow that connects the CRM to the finance system. When you change one thing in this environment, it affects other things. The person who changes it needs to understand the whole.
Institutional clients, NGOs, and mid-market businesses in East Africa also face a specific challenge: technology partners who are good are rare, and the good ones are usually occupied. A project engagement rents their attention for a few months and then loses it. A retainer holds it permanently. In a market where finding a replacement after a project closes can take six months, the retainer relationship is also a supply chain decision.
What The First 90 Days Of A Retainer Look Like
The first 90 days of a Yutie retainer are different from the first 90 days of a project. A project in its first 90 days is racing toward a deliverable. A retainer in its first 90 days is building the baseline that everything else will be measured against.
The Shalom Score is calculated at the mapping session before month one begins. Every domain is assessed. Every domain gets a state: Tending, Waiting, or Quiet. The priority sequence is agreed: which domains need active work first, which can wait, which are stable enough to monitor without intervention. This priority sequence is the first 90-day plan.
By the end of month three, the standing partner has:
- A documented understanding of all eight domains, not just the one the owner hired for
- Three months of Shalom Score history, enough to see which domains move easily and which resist
- A working relationship with the owner that includes communication style, decision-making pace, and the ability to disagree productively
- A clear picture of what the next 12 months of the technology environment should look like
A project team at the end of month three has a deliverable. The retainer partner at the end of month three has something harder to build and more valuable: understanding.
The Honest Difficulty Of The Model
Standing partnerships require more from the owner than project engagements do. A project can be managed at arm's length. You give the brief, you review the outputs, you pay the invoice. A retainer requires ongoing engagement. Monthly strategy sessions. Honest reporting on how the domains are actually performing. Willingness to hear when an intervention did not work and needs to change.
Some owners are not ready for this. They want a partner who will build things and not ask too many questions about the broader environment. The standing partner model is not designed for them. It is designed for owners who understand that their technology environment is a living system that needs continuous attention, not periodic builds.
The Shalom Score exists precisely to make this ongoing engagement concrete rather than vague. It gives the monthly conversation a structure: here is what was scored, here is what changed, here is what the next cycle should address. Without that structure, the monthly strategy session becomes difficult to run and easy to skip. With it, the session has clear inputs and clear outputs every time.
What This Means For How Technology Is Priced
Project work is priced by scope. Retainer work is priced by access and continuity. These are fundamentally different things, and they attract different clients.
A business that is shopping for the cheapest way to build a website is not a standing partner client. A business that understands that their website is one component of a Presence domain that also includes their search visibility, their listing management, and their digital reputation, and that the Presence domain is one of eight domains that together determine the health of their technology environment, and that all of that needs a single person who understands it all and holds it month after month, that business is a standing partner client.
The pricing of the Yutie retainer reflects this. Foundation at KES 45,000 per month is not cheap for a business that thinks about technology as an expense. It is reasonable for a business that thinks about technology as infrastructure. The distinction is not about the price. It is about what the owner believes their technology environment is for.
The Question Worth Sitting With
If you removed your current technology partner tomorrow and could not hire their replacement for six months, what would break, and how quickly? If the answer is "not much, we would be fine," your technology environment is probably simple enough that the standing partner model offers limited additional value. If the answer involves a list of things that would begin degrading immediately, you already know you need someone holding it. The question is only whether that holding is happening or not.
