Customers often ask us the same question before they start a project: "How will you actually work with us?"
Until now, the honest answer lived in our team's heads. Today we are putting it in writing. We have published our Delivery Playbook, a plain description of how TechSoft takes a problem to working software, who does what, and the rules we follow along the way.
It is part of a bigger update to techsoft.one. We have also reorganized our services and industries pages, redesigned our case studies and rewritten much of the site in plainer English. But the playbook is the piece we are most excited about, so this post is about that.
Why we wrote it down
A way of working that exists only in people's memory is fragile. New team members have to guess. Customers cannot see what to expect. And when a project gets stressful, it is easy to forget the habits that keep it healthy.
Writing the playbook gave us three things:
- Predictability for you. Every engagement follows the same stages, the same weekly rhythm and the same quality checks, so you know what happens next and when you will see working software.
- Clear ownership. Each activity has one role that answers for it, on both sides. You always know who to ask.
- A shared standard for our team. A new engineer or manager can join without the project depending on one person's memory.
Built on our four values
We behave, manage and are guided by our core values: Kindness. Sustainability. One-Team. Excellence. The playbook is where those words become habits. For example:
- Kindness: retrospectives look at how we work, not who to blame, and bad news is shared early, with options attached.
- Sustainability: we work in one-week sprints at a steady pace, and every change is understood by an engineer before it ships.
- One-Team: your team and ours share one backlog and one status report. Your product owner takes part in planning and review.
- Excellence: four quality gates stand between an idea and production, and we measure results against a baseline we agree with you at the start.
Every page in the playbook shows which values it reflects.
Five stages, one-week sprints
Every engagement moves through five stages: Discover, Design, Build, Verify and Operate. Each stage has a clear goal and an exit check that we agree with you before moving on.
Inside the Build stage, we work in one-week sprints. With AI-assisted engineering we can produce features quickly, so we plan on Monday, review and release at the end of the week, and send you a weekly report. Small, regular releases mean you see progress early and can change direction cheaply.
Who does what
The playbook describes every role on a project, on your side and ours, and how they connect. A few things are specific to TechSoft:
- On your side, the CEO is the sponsor: the person who decides and signs off.
- On ours, the Delivery Manager runs the engagement, the plan and the weekly rhythm.
- Our CTO looks after security, compliance, and how we use AI and data.
- We do not have a separate Business Analyst. Our designers, Tech Leads, engineers and QA engineers share that work, because people who use AI coding tools such as Claude Code get far better results when they understand the customer's business themselves. You still confirm every requirement.
How we use AI, in plain words
We use AI every day, and it makes good engineers faster. The playbook sets out simple rules so that speed does not cost you safety:
- Only approved tools are used on your code and data.
- Secrets and regulated data stay out of AI tools unless the policy says otherwise.
- Every AI-assisted change is reviewed by an engineer who understands it.
- AI never decides on architecture, security or business questions, and it never approves a release.
What is in the playbook
The playbook has 20 short pages, with a menu on the left so you can jump around:
- Start here: our principles and how the team is organized.
- Roles: customer and leadership, product and design, engineering, and quality and operations.
- Lifecycle: the five stages, with a page for each.
- Working agreements: decision rights, meetings, and what "ready" and "done" mean.
- Quality and AI: quality gates and AI-assisted engineering.
- Services and governance: how the playbook adapts to each of our services, how we escalate problems, and how we measure and report.
Read it, and tell us what you think
We wrote the playbook to be used, not filed away. If you are thinking about working with us, it is the clearest picture of what the first weeks will look like. If you already work with us, we would like to hear where our practice does not match the page. That is how we will keep improving it.
Read the Delivery Playbook or talk to us about your project.
