Before the demo, here are the straight answers.
If a question is not answered here, bring it to a pilot conversation. The honest answer is better than a confident piece of fog.
Who is TinKan for?
TinKan is designed for teams running multi-partner, funded or otherwise accountable projects where a project manager needs a current view of delivery across people, workstreams and responsibilities.
Is it a replacement for every system we use?
No. It is not intended to be an ERP, finance system, specialist scheduling tool or a giant all-purpose collaboration suite. It is a clearer operating view for project delivery.
How does setup work?
During the founding-project pilot, TinKan assists with initial project structure, role configuration and onboarding. The aim is to have a live project working quickly, not to turn configuration into another project.
Who owns our data?
Your organisation retains control of its project data. The pilot includes a clear exit route and data export support if TinKan is not the right fit.
What support is available?
Pilot organisations receive direct support and a regular review rhythm. The pilot is partly about learning which support and documentation make rollout genuinely easy.
Is TinKan suitable for a tiny personal task list?
Probably not. There are excellent simple task-list tools. TinKan earns its place when teams, responsibilities, handovers and reporting need to stay coherent.
Can we assess project health before applying?
Yes. Download the project-oversight checklist below. It is intentionally product-neutral; if your project is already in good shape, that is a win regardless of whether you use TinKan.