The first conversation with a new client tells you almost everything about how the rest of the project will go. Not because of the idea they bring, ideas change constantly once real work starts, but because of how clearly we set expectations from that very first call. At Abango, managing a client project is not something that starts after the contract is signed. It starts the moment somebody says "we want to build something," and it is my job to turn that excitement into a process everyone can actually follow.
The first call sets the tone for everything after it
In that first call, we are not selling. We are listening, and asking the questions founders do not always enjoy answering: who is this actually for, what happens if we do not build this, how will you know it worked. We also say, plainly, what a realistic timeline and budget look like for what they are describing. Founders sometimes arrive expecting a sales pitch and get a working session instead. It surprises people, but it is exactly why the projects that make it past that first call tend to go the distance.
Every project gets one home, not five scattered WhatsApp threads
Nothing kills a project faster than important decisions living in someone's WhatsApp chat, buried between a family group and a jollof recipe forward. Every client project at Abango gets one dedicated channel, one shared document tracking decisions, and one person, usually me, responsible for making sure nothing important gets lost in casual conversation. It sounds basic, but you would be surprised how many projects elsewhere fail simply because nobody could later agree on what was actually decided.
"If a decision only exists in somebody's memory of a phone call, it did not really happen. Write it down, or it is not real."
Concretely, that home is a small, boring stack that does not change from project to project: Notion for the roadmap and decisions log, Jira for the actual sprint work, Productboard for turning scattered client requests into something we can prioritise honestly. Figma stays open so design and scope are always the same conversation, GitHub tracks the engineering side, and Google Workspace handles the everyday admin of calls, docs, and calendars with the client. Claude and ChatGPT sit underneath a lot of that, drafting the first pass of a spec or a status update so I can spend my time refining it instead of staring at a blank page.
Scope creep is not evil, it just needs a name and a price
Clients change their minds. That is normal, and honestly, it is often a sign they are paying close attention to their own product. What is not normal is pretending those changes are free. When a request comes in that was not part of the original scope, we do not quietly absorb it and hope nobody notices the deadline slipping. We name it, explain what it will cost in time or money, and let the client decide with full information. That single habit has saved more client relationships than any clever negotiation trick ever could.
We show progress weekly, not just at the end
There is a particular kind of anxiety that builds up when a client has not seen anything for three weeks and does not know if their money is being well spent. We avoid that entirely with a simple weekly rhythm: a short demo or update, even if the update is "here is what slowed us down and here is the new plan." Clients do not actually need constant good news. They need to trust that we will tell them the truth on a predictable schedule, whether the news is good or not.
Handover is a checklist, not a goodbye
A project is not finished when the last feature ships. It is finished when the client can actually run it without us, or knows exactly what support looks like if they cannot. Documentation, access credentials, a walkthrough of how everything fits together, a clear support plan going forward, all of it is part of the same process that started with that first honest phone call. Good project management, in the end, is not a separate skill from good engineering. It is the discipline that makes good engineering actually land in a client's hands, on time, without surprises.