A versioned brief
Prose sections in your own words, your glossary first, explicit non-goals, and a way to tell whether the one thing it must do has been done. Re-running discovery writes a new version; it never overwrites the old one.
Pisteyo · invitation only
One guided call.A finished brief.Ready to build.
Autolace is how Pisteyo runs product discovery. You talk about your business. The app asks the questions, and your product takes shape on the screen while you watch. By the end of the call there is a versioned brief, every assumption on record, and a build code a build system starts from.
Sign inNobody self-serves. Pisteyo sets the session up.
Round 1 · Shape
Who is actually in the room when an order gets placed?
- A rep, standing in the store
- The store owner, on their own
- Someone at head office, after the fact
- Nobody. It arrives by text message
Something else. Say it in your own words.
Your product
RepStore ownerOrder deskPlace an opening order
Redrawn after round 1The shape of a session
0Minutes, roughlyOne call. The operator drives, you talk about your business, and the screen keeps up with you.
0Parts of the briefFrom what it is and who uses it to the money rules and the one hard constraint. The interview stops when they are covered.
0Speakable build codeMinted the moment the engagement is created, and short enough to read out loud on the call.
0Write-ups afterwardsThe deliverable is finished when the call is. Nothing is owed after you hang up.
What it is
An interview that writes the spec
Autolace turns a spoken idea into a product specification on a single call. The operator shares the screen, and the app interviews you about your business. Plain questions, multiple choice, one at a time, each one written from what you just said. Nothing to prepare, nothing to fill in.
You answer out loud and watch it land. The brief writes itself section by section, a diagram of your product redraws as you correct it, and every assumption gets written down in front of you, waiting to be challenged. It is your product, appearing at the speed you can describe it.
Sign inIf Pisteyo invited you, this is the door.
The arc of a session
A chat window that becomes a workspace
Nothing is hidden and nothing is performed twice. Each panel arrives on the round that first gives it something to say, in the space the page already had, so a room watching a shared screen always has exactly one place to look.
Round 1 · Shape
Who is actually in the room when an order gets placed?
- A rep, standing in the store
- The store owner, on their own
- Someone at head office, after the fact
- Nobody. It arrives by text message
Something else. Say it in your own words.
Why the screen is shared
“No, that part's wrong.”
A shape of your business is drawn on the shared screen seconds after you describe it, so the part that is wrong is visible while everyone is still in the room to say so.
A diagram nobody argues with has not done its job.
A session
An operator drives. You just talk.
You are never handed a form and never asked what you want built. An operator from Pisteyo drives while you talk, and types on your behalf when it is faster, recording the sentence you actually said.
Every question is multiple choice with a free-text escape, and the options teach: someone who has never considered per-store price tiers learns that the axis exists by being offered it. It stops when it has covered the ground, not when it runs out of enthusiasm.
What a session produces
Three things, before the call ends
Every assumption, on record
Every decision nobody was asked about, written down as one plain line you can correct in thirty seconds. An unasked question is a silent risk; a declared assumption is a visible one.
A build code
A short code you can read out loud on the call. One authenticated request hands a build machine the whole bundle, or names exactly what is still missing. There is no third outcome.
Sign inAll three exist by the time the call ends.
What we are assuming
Every unasked decision, written down
An unasked question is a silent risk. A declared assumption is a visible one. Anything the conversation decided without asking you appears in this list while the call is still running, in one plain line you can correct out loud.
Correcting an entry never deletes it. The correction lands as a new line and the original stays underneath, struck through and still readable, so a builder can see what changed and when.
- 01
An opening order means a store’s first order of each drop, not their first order ever.
An opening order means a store’s first order ever.
Corrected by the client - 02
Volume breaks are worked out per style, not across the whole order.
Taken as read - 03
A rep sees their own stores only, and head office sees all of them.
You agreed - 04
A credit check has to clear before a wholesale account can place anything.
Needs a decision before anyone builds
Who it is for
People who know their business, not software
You are the expert in the room. Nobody will ask you what a role is, how the data should be structured, or what you want built. You will be asked about reps, stores, drops and referrals, in your own words, one question at a time.
Everything you say is confidential business information. It is never sold, never used for advertising and never used to train a model, and no session content travels in an email. The privacy policy names every company that touches it, including the one that computes search vectors, which is a separate call from the model running the conversation.
Your call is booked. This is where it happens.
Sign in with the address Pisteyo invited. If you were not invited there is no way in from this page, and that is deliberate. If something is wrong before the call, the support form reaches a person.
Sign in