How an engagement runs
Every package follows the same idea: see first, then build, then hand over. No phase where I'm off writing somewhere else — I'm on site, and what I build follows from what I find with you.
The first day
I don't start with a presentation, I start by watching. I shadow the people who do the work every day: how does an order come in, where does someone update a spreadsheet, which step costs time every single time. I ask what systems exist — an accounting package, a CRM, a planning tool — and what data sits in them.
Mostly I listen for where it hurts: tasks done twice, information that never comes together in one place, something everyone agrees "needs sorting out eventually" without anyone finding the time. Those are usually the spots where a small tool makes the biggest difference.
By the end of the first day I have a concrete picture of what's there and a first estimate of what's worth building. I check that with you straight away — not only at the end of the engagement.
How I choose what to build
I don't pick a technology upfront and then look for a problem to fit it. I look at three things: how much time or how many errors a task costs today, how good the underlying data already is, and whether a solution can genuinely be finished within the time the engagement allows.
That can turn into a script that automates a recurring task, a dashboard that brings scattered data together, or a link between two systems that are separate today. The shape follows from what I find, not from a fixed menu.
If it turns out during the engagement that something else pays off more than what we agreed upfront, I discuss that with you — the goal is that something useful is running, not that we finish an original plan at all costs.
What handover means
Before I leave, I explain how everything works to the people who will use it: where the code or configuration lives, how to change something, and what to do if something breaks. No technical document that only I understand.
The goal is that your own people — or your existing IT partner, if you have one — can carry it forward without having to call me back in. Want to keep building together with me anyway? That can happen through individual days, without needing a new engagement for it.
What I expect from you
One fixed point of contact on your side, who plans the days with me and stays reachable for questions during the engagement — not necessarily the owner or management, but someone who knows the work and the systems.
Access to the systems and data that are relevant: a login for the accounting package, an export from the CRM, or simply someone who can let me look over their shoulder at how a process runs today.
And time from the people who actually do the work — not the whole day, but enough to answer questions and test the result together before I leave.
Ready to see if this fits you?
Half an hour is enough to know whether Kufu can do something for you.