Project planning
Clarify the problem, users, constraints, and priorities. Leave with a defined direction and a plan for delivery.
How We Partner
A clear way to work together.
Start with a clear plan, bring a project to life, or work with us over time. We agree what needs doing, who is responsible and how we will keep you informed.
How We Partner
Product delivery
Bring strategy, design, engineering, and testing together around agreed milestones, demos, and launch preparation.
A team that works with yours
Add product, design and development skills to your team, working from the same priorities.
Support & improvement
Keep your software working well after launch, with agreed support, maintenance and improvements.
Make responsibilities clear from the start.
For each engagement, align the delivery plan with your operational requirements. These are the decisions we work through together.
Scope & visibility
Agree milestones, decision-makers, review points, and how changes affect time and cost.
Security & quality
Define access, data handling, testing, and release requirements for the systems involved.
Ownership & continuity
Document code and infrastructure ownership, handover, support responsibilities, and escalation in the agreement.
Before we begin
Where is Tinker based, and who do we contract with?
Tinker Digital is a US-registered company with contracts under US law. The engineering, design and delivery team works from Nairobi, Kenya. You get one agreement and one accountable team.
How do time zones work?
Nairobi is UTC+3, which gives a shared working window with Europe all day and with the US East Coast every morning. Engagements run on written daily updates and a scheduled weekly demo, so progress never depends on overlap.
Can you work with our existing team?
Yes. We can work alongside your product, engineering, and business teams. Discovery establishes responsibilities, communication, and the capabilities needed.
How are cost and timing agreed?
We first review the problem, constraints, and scope. The proposal sets out delivery milestones and commercial terms. Changes are reviewed for their effect on time and cost.
Who owns the work?
Ownership, access to repositories and infrastructure, third-party licences, and handover are addressed in the engagement agreement before work starts.
What happens after launch?
We can plan ongoing maintenance and improvements. Support hours, incident escalation, and service commitments are agreed for the specific engagement.
Which of your systems don’t talk to each other?
Bring the systems, bottlenecks and goals you want to discuss. We will help identify a practical first step.