From an account to your first board.
You need no credit card and no conversation up front. The first project is free; what happens with the second is on the pricing page.
8 steps, and you are standing on your own board.
Create an account
One click with Google, Microsoft or GitHub — nothing to invent, nothing to remember. Prefer your own password? That works too, with your work e-mail. If Turnado recognises your e-mail domain from an organisation that already exists, it suggests joining that one instead of starting a second empty tenant.
Confirm your e-mail address
Only with your own password: you get a confirmation link then. Anyone coming in through Google, Microsoft or GitHub has already been verified there and skips this step — that saves an e-mail and a wait.
Your organisation
An organisation is the tenant and the invoice holder: all data carries its id. Without an organisation there is no place for your work to live.
Terms and permissions
Turnado‑1, our own process model, learns from process runs — and that needs your permission, asked once and changeable at any time. Your source code is never used for it.
Your first project
A project keeps the tickets, the repository and the model choice together. You can skip this step.
Your code
Without a repository everything works except the code work: no branch, no pull request, no gate facts. This is where the AI colleagues write. You can skip this step.
Your AI model
The AI colleagues run on a model from Claude, GPT or Mistral — with your key. Without a key the board simply works, but the AI colleagues politely refuse. You can skip this step.
Add colleagues
Viewers and customers do not cost a seat, so feedback never has to stay outside the board. You can skip this step.
An analysis document in, a backlog out.
Signing up puts you in the chat, and that is where it starts: drop your analysis or functional design in there. Turnado turns it into epics, features and user stories with acceptance criteria, and says which contradictions it ran into in the document instead of filling them in silently. What comes out is on the board, not in an answer pane.
No document yet? Then describe what you want to build and the AI analyst asks its questions; under every answer sits the button that submits it as the analysis document. The intake form remains the direct route for text you already have.
After that it is an ordinary project. You plan a sprint, you assign work to people and to AI colleagues, and you move statuses. You notice the difference at the first transition that is not allowed: it says word for word which condition is still open.
A document, and a repository if you already have one.
An analysis or functional design is enough to start; the board fills itself with it. For the code work you connect a Git repository — then the AI colleagues work in their own working directory and open a pull request that you review and merge.
Without a repository the rest works fine: chat, intake, backlog, sprints, statuses, gates, hours and usage. You only miss the part that touches code.