// HOW IT WORKS
How it works
A clear, straightforward process from the first conversation to a specialist working within your team.
Bringing someone new into your team is an important decision, so we keep the process short and clear. You tell us what your team needs, and we recommend people and levels. You meet them before anything is agreed, they start, and we check in regularly to confirm the arrangement is working. The sections below describe each part of the process.
Team composition and levels
Some clients need one experienced person, such as a senior engineer to improve code quality, a tester to establish automation or a delivery lead to bring order to planning. Others need a small team that can take responsibility for a whole area of work.
Where the problem calls for it, we will usually recommend a team. People who already work well together become productive sooner, and a mix of skills covers more of the software lifecycle. The decision is yours, however. You choose how many people you engage and at which levels, and you can start small and add people later.
We grade our people by what they can do. Years of experience reveal little on their own: one person may spend a decade doing the same work, while another spends three years building and running real systems and develops quickly. Each level describes what a person can be entrusted with and what they bring to your team. We share a document setting this out during our sales conversation, so that you can choose the right level for the work rather than paying for a title.
How an engagement starts
Every engagement follows broadly the same path. We keep the administration light, because neither party benefits from weeks of paperwork before useful work begins.
- An initial conversation. You tell us about your team, your product and what is not working. We ask detailed questions and tell you honestly whether we are the right fit.
- A proposal of people and levels. We recommend specific people, at specific levels, and explain why. If we would recommend a team, we say so and set out our reasoning.
- An introduction. You speak with the people concerned before anything is signed, ask them whatever you wish and decide whether they suit your team.
- A start date. They join your stand-ups, receive access to your tools and take on real work as soon as that access is in place.
- Regular check-ins. We speak with you and with our people at regular intervals, so that small issues are raised early and resolved quickly.
Contract and pricing
Contractually, this is staff augmentation: our people join your team under a contract with us, and we remain responsible for their employment. Day to day, they work as part of your team. They follow your process, use your tools, keep your hours and report to whoever you nominate.
What you are engaging is expertise: people who do the work and improve how your team does it, so that the team is in a stronger position when they leave.
We run a deliberately lean company. There are no layers of account managers between you and the people doing the work, and you deal with them directly. This keeps our costs down, which is reflected in what you pay. We discuss pricing in the first conversation, once we understand what you need.
// FAQ
Frequently asked questions
Can we start with one person?
Yes, and many clients do. If the arrangement works well, adding people later is straightforward, and the person already with you helps new team members settle in.
What happens if the person is not a good fit?
Tell us as soon as you notice. We will speak to both sides, and if the situation does not improve we will propose someone else. The regular check-ins are intended to identify this early.
Will they work our hours and use our tools?
Yes. They are based in South Africa, keep your working hours and work in your repositories, issue tracker and chat. On-site days can be arranged.
Why do you not publish your rates?
Because the appropriate figure depends on how many people you need and at which levels. We prefer to understand your situation and give you a clear quotation rather than publish a table that suits no one in particular.
// RELATED SERVICES