A delivery prediction for every project — and you could have it tomorrow.
More lightweight than your current approach — minutes to set up, one click per confidence vote for your team, real insight from the start.
Before you start: a quick orientation
The heart of Genchi is the initiative — a goal, a deadline, and a team. The initiative is kept current by a regular confidence vote from each team member, which predicts whether the goal will be met by the deadline, and highlights problems early.
Setup
Four steps: sign up, set up your company, create your first initiative, connect your tools.
1. Sign up
- Register with email, or sign in with SSO. Use your work email and a password, or sign in with Atlassian or Google.
- Or use an invitation link. If a team has invited you, click the link to join their company directly.
- Slack-only voting. Invited via Slack? You can respond to confidence votes from Slack alone — but registering an account lets you see the dashboards and team views.
2. Set up your company
- First user? Register your company — provide the company name and URL. You'll become the first admin.
- Joining an existing company? Select it during sign-up. An existing admin just needs to approve your request.
- No need to wait. You'll have full use of the system, but won't see other teams or existing users until approved.
3. Create your first initiative
- Every initiative has an Owner. The Owner sets the goal, the deadline, and the voting cadence.
- Invite the team and observers. Team Members are prompted to respond to the regular confidence votes; Observers can follow progress but aren't asked to vote.
- Build hierarchy if needed. Related initiatives can be linked into project trees using a parent-child relationship.
4. Connect your tools
- Slack — the best and easiest way to vote. Connect your Slack workspace so voting happens where your team already is.
- Jira and Asana — import existing details. Pull projects, issues, and users into Genchi as initiatives. Save the setup time.
- More integrations. See the Integrations page for the full list — including SSO. More coming soon.
Operational
A better way to track status — built on a simple rhythm where everyone has their part to play.
Team Member
Individuals who are doing the work.
- Vote when prompted. It's one click, about two seconds — and if you miss one, your previous vote carries forward until you update it.
- Be candid. Express your honest opinion. You might be seeing something no one else is.
- Confidence naturally shifts. Your confidence is expected to change as problems are encountered and resolved. Real life isn't 'green' all the time.
Initiative Owner
Typically the team leader or project manager.
- Set a clear goal. When creating an initiative, describe a goal with a clear success outcome — so votes have something to measure against.
- Add context with comments. Drop a comment when something would help observers and stakeholders understand the situation better.
- Welcome the bad news. Encourage your team to flag problems early. Catching issues early is when you can still affect the outcome.
Observer (Stakeholder)
Engineering leadership or interested parties from other teams.
- Watch for dips in confidence. A drop in the team's signal is a flag that something may need attention.
- Don't over-react. Problems are encountered and resolved in every project. Your role is to know — not to micro-manage.
- Step in when it matters. Use this awareness early — when additional resources or a change in scope/deadline could actually help.
Admin Users
One or more users designated to manage the account.
- Manage users. Individuals and groups may request to join at irregular intervals — approve or decline these in a timely way so people aren't kept waiting.
- Manage integrations. Configure and maintain the connections to Slack, Jira, Asana, and the SSO providers your company uses.
- Manage billing. Keep payment details current and adjust the plan as your team grows.
Stop making the status report the worst part of the week. There's a better approach.
A 1-click confidence vote provides a more practical and actionable alternative to your current project status reporting process.
START FREE TRIALFree for teams up to 10. Larger teams from $2.50/user/month (~$250/month for a 100-person org). No credit card to start.