Upload a contract, get a video explaining it

Five steps, from your own words to a build

The flow is the same for a supplier agreement, a lease, a term sheet or a settlement, and it is the same five steps that build a course. You say what you need, you answer the questions that come back, you attach the document, and you choose the runtime last.

• Describe. Pick the shape - one concept, a whole subject, or content you hand over - and say in your own words what you need. Rough notes are fine.
• Refine. Three to five questions, planned from what you just wrote: what you are deciding, who it is for, how much of it to cover, how careful the wording has to be. Every one of them is optional.
• Focus. Pick what this has to achieve, or write your own line instead. Selecting nothing is an allowed answer.
• Files. The step the agreement is attached at - step four, not step one, so the questions come from what you said rather than from the file.
• Review. Name it, pick the runtime and the depth, read what the build will cost in minutes against your balance, and send it.

What a walkthrough looks for

Every agreement has a few places where the money, the exit and the risk are decided. The walkthrough is planned around the ones your question points to. These are the four it is planned around.

• The price you agreed to is not the price in year two. That number lives in a schedule at the back.
• Getting out of it has a notice period, and the notice period has a date.
• Somewhere in here is what you promise to cover if something goes wrong, and how much of it.
• One clause decides whether this is exclusive. You will be asked about it later, by your board.

What comes back

A narrated video in chapters, one question each. A chapter states the finding in plain words and names the clause it came from, so you can open your own copy at that clause and read the words yourself.

The chapter titles are decided by the build worker when your job starts, from your own words and from whatever text it was handed. The shape named here is the fallback it uses when that call does not come back - not a list you are promised, and not one you approve before the build begins.

Minutes are the only meter, and a build costs exactly the runtime it produces: a 15-minute walkthrough spends 15 minutes of your monthly allowance. The content track opens at 15 minutes and the ladder runs to 30 hours. The pricing page lists what each plan grants and what a top-up adds.

If a chapter moves too fast, or you need a different clause covered, you say so in plain words and that starts a new build. The new build costs the full runtime of that video in minutes all over again, the video you already have is kept exactly as it is, and what the new build hands back is another sample file.

Not legal advice, and why that is the point

We are not your lawyer and this is not legal advice. This is so that when you do talk to your lawyer, you already know which three pages to talk about.

A walkthrough does not tell you whether to sign, does not score the contract, and does not predict how a clause would play out for you. It shows you what your document says at the places that matter, and names the clause. What you do with that is between you and your lawyer, and the conversation starts further along.

Where this build stands

Four things are true of this build today, and each one is shown in the flow rather than in a footnote.

Early build: we save your request and plan the course. No course video is generated yet - a finished build hands you a sample file, not your course - and we will tell you the day that changes.

You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it.

Payments are live. A plan is a recurring monthly subscription and a top-up is a one-time charge, both taken through Stripe Checkout, and your card details never reach ZUQ.

Early build: an update request spends real minutes and hands back another sample file, not your rendered course. The video you have now is kept exactly as it is, and we will tell you the day real rendering begins.