Skip to content

Unblock yourdevelopers.

Bring your product team into one session. Scopeleaf asks the questions nobody asked, builds the prototype, and hands engineering a feature they can start on.

Get started

Book a demo

Thirty minutes, on your own feature.

Bring one epic or one rough ticket. We run it through a session together, and you leave with the feature prepared.

Leave your work e-mail and our team will write to you to find a time.

We use these details only to answer you. Privacy policy

Made for the people who decide what gets built

How it works: one feature, from a rough idea to ready

  1. It starts with people.

    Four people and one rough idea: an epic, still in discovery.

  2. Written together, live.

    The epic's first feature, with its acceptance criteria, in one shared document.

  3. Questioned before it is built.

    GrillMe interviews the team, round after round, until nothing is silently assumed.

  4. Decided, not discussed.

    Every answer becomes a decision in the ticket. Nothing is left to argue about.

  5. Clicked before anyone builds it.

    The feature as a prototype on a phone, made from the ticket alone.

  6. Ready to build.

    Saved to its project and checked against the features already there.

  7. Ready to implement.

    The three words every product owner wants to read.

Scopeleaf helps your team before, during and after GrillMe.

Before GrillMe

Can’t we just write it in Jira?

Write it together, from one link.

Start from a ready template. Share one link, and everyone who opens it writes in the same document, at the same time.

Maya picks the Feature ticket template, and the document opens with its sections: Short Summary, Reason Why, Target Group, Acceptance Criteria. She copies the Share link; Jonas and Priya join, and both write at once, each with their name on their cursor.

Before GrillMe

Do we have to talk about Production again?

Tell GrillMe what doesn’t apply.

Every area starts on. Switch off what this feature doesn’t need, and the interview won’t ask about it. Next time starts from your choice.

Before the interview starts: “What this grooming covers”, 14 of 14 areas on, in five groups: Deployment, Test types, How it is tested, Quality and Acceptance. Maya switches off Simulator and Scalability, 12 of 14 are on, and she starts the interview, which shows “Off in this grooming: Simulator, Scalability”.

Grill me starts the interview, with the whole team in it.

In GrillMe

Can’t I just run grill-me in Claude Code?

One question at a time. Lost? Ask for simpler words.

GrillMe asks, and one person answers for the team. Anyone who is lost presses I don’t understand, and the same question comes back in plain words, for everyone.

Question 3 of 5: “Should the pairing token be bound to the hub’s BLE identity or to the user’s account?” Jonas presses “I don’t understand”; after “Finding simpler words…”, a box “In simpler words” opens above the options: should a phone work only with that one hub, or with any hub on the account.

In GrillMe

Talk one question through before you answer.

Every question has its own Discussion. Dig deeper with the AI; the operator decides whether the interview hears it.

Question 2 of 5, with its Discussion beside it. Jonas asks how long the hub keeps a half-finished pairing; the Discussion replies that it keeps it for two minutes. Maya, the operator, presses “Use this in the interview”, and the reply is in the interview’s background.

In GrillMe

Coming soon

Ask the people who aren’t in the call.

Send the open questions to the colleagues who couldn’t join. Their answers come back into the session.

The question queue, five questions, three of them open, and a survey for people who aren’t in the call, with its link. Maya copies the link; Ola from Support answers, and the three open questions come back marked as from the survey.

Finish the interview and Scopeleaf prepares the final version for your team to review.

After GrillMe

Who rewrites the ticket after the meeting?

The final version, ready to accept.

Scopeleaf prepares it by itself. Accept it, and put it in its project.

Four steps in a row: The interview is finished; Preparing the final version…; Accept final version; Add to project, Smart home app.

After GrillMe

Isn’t a Figma link enough?

A prototype of the right kind.

Scopeleaf reads the ticket and decides what to build: the screens a user sees, an animated diagram of a back-end flow, or both. Every screen says whether it came from the ticket or was assumed.

Building your prototype: Reading the ticket, Writing the prototype, Publishing, each ticked in turn; beside them the brief, “Kind: frontend”. Then the prototype: four screens, each marked from ticket or assumed, a phone preview of “Find the hub”, and Next to “Pick the hub”.

After GrillMe

Coming soon

With a tour for whoever opens it.

Add a tour to the prototype. Step by step, it shows people what they are looking at.

The shared prototype, its “Pick the hub” screen dimmed except one part at a time, with a card beside it: 1 of 3, the hubs nearby; 2 of 3, pick yours; 3 of 3, pair it.

Didn’t we decide this last quarter?

Second Brain

Every grooming, remembered.

The important part of each GrillMe stays: what the team agreed, what is still open, and the terms it named, each with the feature and the grooming it came from. Your next GrillMe reads it, your project’s first.

Correct anything that is wrong: your correction is what later groomings read.

The Second Brain as a map: documents on the left, the groomings they went through in the middle, and what each grooming left on the right, as agreements, open questions and terms. The grooming of “Pair a device from the phone” on 12 October leaves an agreement, a term and an open question, which join the map.

Before Scopeleaf, and with it

Before Scopeleaf

  • The feature is written alone. One person drafts it in Jira. The team sees it later.
  • Answers wait in the comments. A question on Monday, a reply on Wednesday, then silence.
  • GrillMe is for engineers only. It lives in Claude Code or Codex, behind a terminal.
  • Which model? Nobody knows. GPT, Claude or Gemini, and which prompt: everyone guesses.

With Scopeleaf

  • The whole team writes it, live. Product owner, manager, architect and engineer, in one document.
  • GrillMe questions everyone. No terminal. Whoever knows the answer gives it, in the same place.
  • The right model, picked for you. A quick one fixes a typo. A deep one interviews the team.
  • Ready to implement, one hour later. Refined and agreed, before anyone writes code.

From product teams

Helping product people through busy sprints.

Placeholder voices for this preview: AI-generated photos of fictional people and sample quotes, to be replaced with real customers before launch.

  • GrillMe

    “Thursdays used to be chasing answers. Now it’s one hour, and the ticket is done.”

    Marta K.Product owner, payments
  • Prototype

    “Stakeholders click the prototype instead of imagining it.”

    Daniel O.Product manager, B2B software
  • GrillMe

    “Grooming stopped being the meeting everyone dreads.”

    Aisha R.Scrum master, insurance
  • Final version

    “I can finally read a ticket and see what I’m paying for.”

    Tomasz W.Business owner, agency
  • GrillMe

    “One GrillMe round, two answers from me, and I’m out.”

    Elena V.Architect, logistics
  • Final version

    “The edge cases arrive written down. No more surprises mid-sprint.”

    Jonas B.Engineering lead, mobility
  • One link for everyone

    “Guests are free, so everyone with an opinion is in the room.”

    Nora H.Product manager, marketplace

Fits your team

Works with your team, the way it already works.

Bring the people, the tickets and the coding agent you already have.

  • New

    Your editor, wider.

    On a monitor up to 50 inches wide, the draft, a spreadsheet and your panels sit side by side as windows you move. One button brings back the usual layout.

    Widescreen: the draft, a spreadsheet and panels side by side on a wide screen
    Watch: Widescreen, 52 s

  • Start from your Jira ticket

    Paste a ticket’s key or link and tick the fields that go into the draft. Jira Cloud, read-only, no API key.

  • Take it with you

    Download the ticket as Markdown, HTML or Word, or copy it as Markdown.

  • A link for people, an invitation for your agent

    Guests join free from the link. Your coding agent joins the draft by name: it reads, proposes and comments, and people decide.

    Invite your agent
  • The operator approves every change

    Proposals from Scopeleaf AI, a guest, your agent or GrillMe wait in Review changes. Only the host or the operator applies them.

  • New

    Fewer questions from your developers

    Before work begins, Scopeleaf shows what the draft is missing and what a developer would ask. We built it on the first versions of 168,039 features from 893 public Jira projects, and the questions their teams asked once work began.

    Questions about the spec once work began

    • Acceptance criteria41% fewer
    • Test notes25% fewer
    • A TBD left open39% more
    • “It would be nice”38% more
    • Roles mentioned36% more

Trust

Built for professional product organisations.

GDPR

Where your data lives, and how long.

  • REL8, a company in Poland, provides Scopeleaf, under EU law.
  • Sessions are stored in the EU, in Ireland.
  • Closing a session keeps it. Only its host deletes it, and nothing expires on its own.
  • Delete your account and the sessions you host go with it.
  • Jira connects read-only, and its tokens are sealed with AES-256-GCM.
  • Document text is kept out of error reports and analytics.
  • The data processing terms are part of the Terms of Service.

Not everything stays in the EU. AI requests go to OpenRouter and its model providers, which can be outside it, and every request asks for providers that keep nothing. Sign-in, hosting, payments and analytics also run partly in the US. The privacy policy says where, and what protects each transfer.

EU AI Act

Who decides, and who can see it.

  • AI text keeps an AI mark, and shows as not reviewed until a person approves it.
  • Nothing the AI proposes changes the document until the host or the operator approves it.
  • The document shows who wrote what: a person, the AI, or text nobody has read yet.

Planned

Not built yet. Listed so you can see where we are going.

  • PlannedAI processing inside the EU, as an option
  • PlannedSingle sign-on for organisations

Questions

What teams ask before the first session.

All questions
Does AI rewrite the ticket for us?

Yes, as a proposal for your team to review. AI prepares the final version when the operator confirms the end of GrillMe. The host or operator can edit and review each change. They can also choose Accept final version to approve the pending changes and mark the ticket Ready. In Draft, AI suggests changes you can approve or reject. Nothing is applied without approval.

What happens in GrillMe?

GrillMe questions your draft one question at a time. Everyone can propose answers and discuss. The operator the host picks sends the answer that moves to the next question. When the operator confirms the end, AI prepares a proposed final version for your team to review.

What is the optional prototype?

When it helps, the ready ticket becomes a clickable prototype on sample data, built from the ticket and shared with a password link; your team and your client leave notes, and the notes come back to the ticket as comments. A build spends the host's AI points, and a host has up to 5 builds a month. Many tickets never need one.

Do we need a polished brief to start?

No. A sentence, a problem, or a rough feature idea is enough. Choose a template and improve it together.

Can several people work on the same ticket?

Yes. The editor and GrillMe update in real time. Invited guests join free with the host's link and a free Scopeleaf sign-in.

Does every teammate need a subscription?

No. Only the host pays. Invited guests join free, and the AI steps they start in the session spend the host's points. A Starter host can have up to 8 guests in a session; Business has no fixed cap.

Can we use our own AI key?

Yes. Add your own keys, from one provider or several, and set a budget. Scopeleaf still picks the model for each task, and without a key of your own it runs the models for you.

Which integrations are there?

The finished feature goes to Jira, Confluence, Google Docs or Google Drive, or downloads as Markdown, HTML or Word. Jira tracks the work; Scopeleaf prepares it.

What do you keep, and for how long?

Closing a session keeps it and ends access, and the host can reopen it. A session is deleted only when its host deletes it, or deletes their account; nothing expires on its own. Export the result you want to keep outside Scopeleaf. Some things stay in your account until you delete them or the account: prototypes you build, with their notes and a copy of the ticket; your own templates, with the text you saved into one from a document (guests' words included); final documents you accept, with the ticket's text as accepted, guests' words included (closing the session does not delete them, and neither does a guest deleting their own account); your Second Brain, an AI summary of what each grooming you hosted agreed and left open, without the participants' names; your projects' names, descriptions, colours and glossaries; and the boards you make from Home and your projects' and final versions' boards, with what the people you invited put on them and the sections of each of your documents on them, updated from the document each time the board is opened (a document's own board goes with its session; a deleted document takes its frame and those notes off every board). Comments on a board go with the board, and you can remove your own. Deleting your account deletes your own boards with their comments, and keeps your comments on other people's boards, signed “Someone”. Your account and billing records stay while you have an account; after you delete it, billing records stay with Stripe and the subscription dates with us. Exported files, and copies held by AI and other connected providers, follow their own rules. The privacy policy has the full list.

What does it cost?

Starter is €19 a month or €190 a year, and Business is €49 a month or €490 a year, per host and excluding VAT. Mentor, everything in Business plus time with experienced product owners, is priced with you on a short call. Guests never pay.

What are AI points?

Points pay for the AI. Each AI step — a review, a GrillMe interview, a proposal — spends points in line with what it really costs, so a short interview costs less than a long one. Starter gets 900 points a month, about 39 typical features with GrillMe or 14 long ones; Business gets 2,700, about 118 or 43. Your balance is always in the header, and each step's points are in the activity list.

Bring the rough idea. Leave with the ticket.

One focused hour with the people who decide.

Get started

Book a demo

Thirty minutes, on your own feature.

Bring one epic or one rough ticket. We run it through a session together, and you leave with the feature prepared.

Leave your work e-mail and our team will write to you to find a time.

We use these details only to answer you. Privacy policy