Partnerships
I’m open to roles, partnerships, and focused programs where ownership is clear and expectations can be agreed in writing. The models below describe typical structures — not fixed quotes or commitments until we sign something that works for both sides.
Open to senior TPM / delivery roles and Q1 partnerships
Recruiters: role titles, level & industries
How an engagement starts
Whether it’s a role, a partnership, or a scoped program, the path is the same: fit first, paperwork second, delivery third.
30–45 minutes. You share context, constraints, and what “done” might look like. I ask hard questions early.
We decide if I’m the right person — role match, partnership shape, or program scope. If not, I’ll say so plainly.
Employment offer, contractor agreement, SOW, or engagement letter — fees, scope, confidentiality, and IP agreed in writing.
Named owners, first milestones, and how we’ll communicate. Work starts when both sides have signed — not before.
Companies
If delivery and systems keep falling between roles, I can take that seat — and help the team move again.
Individuals
If you want to get better at shipping real platforms, working together is often more useful than another course or framework.
Partners
Bring a scoped problem with real stakes. Commercial or mission-driven work is fine when scope, confidentiality, and fees are documented before delivery begins.
Engagement models
Outlines only. Each engagement is documented in a signed agreement (employment contract, contractor agreement, SOW, or engagement letter) before work starts.
Model 01
Permanent or long-term work as a TPM, Program or Platform Delivery Lead, Systems Delivery Lead, or Engineering Manager for a platform team.
Model 02
Fractional delivery leadership for digital agencies and systems integrators — including past senior backend and delivery work through Big Bold Red on Safaricom Baze.
Model 03
Time-boxed work — migrations, modernization, data platforms, integrations, or reliability recovery — with defined deliverables and milestones.
Model 04
Selective advisory for operators in travel, tourism, media, and NGOs — when systems decisions are costly to reverse.
Model 05
Remote platform and systems support for organisations that bridge continents — similar in shape to work with VFAW — Voices for Animal Welfare (Paris HQ, Africa programmes).
Professional work needs clear paperwork. These are my defaults; specifics are negotiated per engagement.
Scope & changes
Written scope or role description. Material changes agreed before extra work.
Confidentiality
Mutual NDA where appropriate. Client data handled per agreement.
Fees & payment
Rates, invoicing, and expenses defined upfront — no surprise scope without approval.
IP & deliverables
Ownership of work product assigned as set out in the contract (work-for-hire, license, or mixed).
Liability
Liability caps and exclusions per signed agreement; this website creates no liability.
Fit & termination
Either party may decline or exit per contract notice terms if the fit isn’t right.
Full site disclaimer: Terms & privacy.
Fit check
A quick filter so neither of us wastes time — direct, not dismissive.
Step one is a short intro call or message — see the four steps above. Initial conversations are exploratory; nothing here or in email constitutes a binding commitment until a contract is signed.