Modernizing Code, the Kisasa Way

We are different. How many times have you heard that about a company? Double click on that claim, and you usually find very little real reason backing it up. It’s a constant struggle—differentiating your product from the competition.

At Kisasa, our claim of being different isn't just talk—it's backed by action. We were founded on a straightforward desire: to improve upon the work we've been doing for years.

Kisasa values are simple. Be kind, help others, and do what's right.

Apply that to our first guiding principle—show by doing—and you have all the ingredients of modernizing applications, differently.

The Blueprint isn’t just a technical report; it’s a living roadmap that aligns your technology with your business goals, complete with architectural diagrams, business context, and a rationale for every recommendation. Our definition of work (the SOW) is not a zero-trust, paranoid about every hour agreement. It’s a realistic, flexible contract that gives us the ability to go in the direction that’s right.

Let me tell you exactly why Kisasa is different.

Blueprints are the way

Someone once described modernizing a production application as open heart surgery while the patient is awake. It’s scary how true that is. At Kisasa, we’ve done this a lot. So much so that we know two modernization engagements are never the same. Each feature/team/line of business/organization all have their nuances. Each prioritize different areas of the business. Each has their own debt and reasons for needing to keep that service up to date.

We’ve seen this so often that we laid down a single rule about every Client engagement: they always start with creating a Blueprint.

Think of a Kisasa Blueprint like the architectural plans that define how to build a house (also called a blueprint). You would never begin building a home by digging a hole, buying material, and fastening everything together. The reality that rooms share walls and the size of one room affects the size of the next would quickly sink in. Much like the services that make up an application, the walls are all connected.

To architect a house, you survey the land where it will be built. You understand the owner’s vision of their perfect home and their goals for how the home will function. You think about the future of home design and how this home will be used. The materials to build the home are purposefully chosen for how durable they are, how they will be utilized, and (if visible) their aesthetics.

With the blueprints of a home, construction has a plan—a direction. When the framers are building the home, things will arise. Things that the blueprint didn't detail. That's when the experience of the architect and home developer come together.

We can't start a modernization engagement with just a few pre-sales discussions, never including those people who will be most affected by the change, and not understanding the infrastructure we will be building on. That's a strategy of hope, and we all know where that will get you.

First, a Kisasa architect will meet with team members and infrastructure owners. They will have a pre-defined set of questions to get the conversation going. This will lead to discussions with business owners/leaders about their goals. What outcomes do they want to see? Finally the Kisasa Architect will put together a plan of how all the puzzle pieces fit. They will have Systems Designers and other experienced folks at their disposal. The deliverable will be thoughtful, purpose built, and ready for execution.

A single SOW to rule them all

Why does selling modernization services have to be so complicated? Unless this is your first sale, you know what's going to happen. You know the players that need to be involved. Why not start with the right folks upfront and then scale with discovery?

Just like creating the Blueprint at the start of every engagement, our experience drives doing the right thing. This sets everything up for success. But not by applying a strict prescription of team members and hourly costs. Instead, we create a single agreement that defines the idea of a Reserved Team.

The economics take into account that different folks with different skillsets will be needed throughout the engagement. To create the Blueprint, we will need an Architect. Depending on the requirements and nuances, we might also need a Product Designer. Once we have the Blueprint, you might choose to ask your team to execute. In that case, our Architect stays available to help the team get started and explain decisions. If you choose to have Kisasa put the Blueprint into action, we're going to need Software Developers. Depending on the delivery date and scope, we might need quite a few.

The Reserved Team concept simplifies modernization service sales by acknowledging the predictable nature of project requirements. Instead of following rigid staffing formulas, we establish a flexible agreement that adapts to evolving needs. From Blueprint creation with Architects and System Designers to implementation with Software Developers, the team composition shifts naturally. This approach combines a blended hourly rate with a weekly commitment, ensuring the right expertise is available at the right time.

Now let's get something done

Our approach is simple. Let's meet a few times to understand how we are going to work together. Create a statement of work that starts with minimal folks and time to get to a Blueprint. Then expand the team and time based on what we've discovered and your goals.

To get started contact David.