MadAve Homepage
Prototype
No. 01 · The Review Issue For agencies that review work every weekLaunching January 1st MadAve.io · Client feedback, connectedAffiliates
Creative Review MadAve Start with one real project. Be first on January 1st.
Cover art: two hands frame a shot around a creative director at her desk, reviewing a fashion image on a monitor, against a red circle.
Dana Whitfield · Client

Approved — no changes.

Version 2·Emailed to the editor

MadAve Creative Review·No. 01

Creative people didn't choose this work to chase feedback. They chose it to make great work.

We believe their time belongs to creating. So we built Creative Review to bring client feedback into the tools where ideas take shape. More time to create. Less time to chase.

Built inside a working agency and used on live client work every week before it was ever a product.

Panels for
  • Premiere Pro
  • InDesign
  • Illustrator
  • Photoshop
  • DaVinci Resolve
  • Final Cut Pro
  • PowerPoint
  • Figma

The problem we fix

The relay

One client note. Eight stops before the creative sees it. Somebody carries it, usually the most organized person you have, and it's the least creative thing they do all week.

Client
Gmail
Slack
Asana
Drive
Teams
The human router
Creative

Eight stops, five apps, one note.·Red is where a person retypes it

The fix is one link

That labor is real. It is rarely billable.

We believe that time belongs to the work. Not to retyping a note, forwarding a thread, or asking which version this is.

Your numbers, not ours

Drag, or type your own

hours a week relaying feedback
$ loaded hourly cost
weeks a year

$18,720 a year

of capacity, before a lost version or an extra round.

Creative Review is $49 a month for one, $199 for a team of up to ten.

Six hours is conservative. 57% of creative teams spend more than a quarter of their time on work that isn't creative. Monotype & Extensis, Scaling Creative Operations, 2025.

The same numbers, as one year of working weeks

7.8 working weeks

of someone's year go to the relay: 312 hours, 39 working days.

The fix·The feedback loop

What if the review stayed connected to production?

The note goes to the work. The client gets one link. Nobody retypes anything. Version 2 returns to the same review.

The feedback loop, drawn on the MadAve e. mark A red note travels the brushstroke of the e: from the client at the ball terminal, along the crossbar where the note lands on the work, once around the eye as version 2 returns to the same review, and out to the red period, which is the approval. Client · One link Back to the client The note, on the work 00:00:12:04 Edits made Internal sign-offs Approved 6 1 2 3 4

Six stops. Drag the playhead, or tap one.

Review opensApproved

1 · Client The client opens one link in a browser. Nothing to install, nothing to learn.

How it works

Client feedback, connected to the people making the work. One loop, three steps.

  1. 1

    The client gets one link.

    Open it in a browser. Pause the cut and type the note at that frame, or say it and it's transcribed. Circle it on the page. Attach a file. Every project you share with them lives behind the same link.

  2. 2

    The note lands where the work happens.

    A red marker on the timeline in Premiere Pro, at the exact timecode. A numbered mark on the layout in InDesign. The creative answers from there, asks from there, and marks it completed from there. Green means done.

  3. 3

    One decision ends the review.

    Changes needed, or approved, with the client's name on it. Either way the editor is emailed, the project manager sees the whole thread, and nobody carried anything. Version 2 returns to the same link.

I · For video

In the edit

The same note, in the client's browser and on the creative's timeline. Nobody carried it.

Both screens work. Draw on the client's frame and it lands on the creative's timeline.

One press plays a whole review: your client's note, your editor's change, the sign-off.

Start on the client’s screen. Pick the square or the arrow, drag on the frame, and say what should change.

This is what the client sees.One link in a browser. Nothing to install.

MadAve Creative Review Truly Being Alive
0:28 / 1:01

This is what the creative sees.Premiere Pro, with the Creative Review panel.

Truly_Being_Alive_60
Program: Truly Being Alive 16x9
00:00:28:12 00:01:01:12
MadAve Creative Review
MadAve Creative ReviewPremiere Pro v0.1.11
Truly Being AliveSequence: Truly Being Alive 16x9
V2

4 added · 0 updated · 0 already on timeline. Save your Premiere project.

Effect Controls
Truly Being Alive 16x9

Dana wants a push-in on the headlight. Drag Scale to about 108, and keep both turn signals in the frame.

One review, both ends·The client's page and the Premiere Pro panel read the way the build does·Nothing you draw, type or change is saved or sent

II · For design

On the page

For layouts, posters and stills: circle it, point at it, say it. Every mark is numbered, and lands in Photoshop or InDesign as a review layer.

Both screens work. Mark up the client's ad and it lands on the creative's layers.

One press plays a whole review: your client's markup, your designer's change, the sign-off.

Start on the client’s screen. Circle something on the ad, press its plus, and say what should change.

This is what the client sees.One link in a browser. Nothing to install.

MadAve Creative Review Tea poster
Page 1 of 1

This is what the creative sees.Photoshop, with the Creative Review panel.

Tea_poster.psd
Tea_poster.psd @ 33.3% (Amazing tea!, RGB/8)
33.3% 1000 px × 1405 px (72 ppi)
MadAve Creative Review
MadAve Creative ReviewPhotoshop v0.1.11
Tea posterDocument: Tea_poster.psd
V2

4 added · 0 updated · 0 already on the review layer. Save your document.

4 to review

Comment 1 of 4 · Page 1

DWDana Whitfield

The headline is the idea and right now it reads like a caption. Take it up until it carries the top of the page. Stop before it gets as wide as the pot.

Circle 1 on the page
Q:DDDemo Designer

Bigger, or a heavier weight?

A:DWDana Whitfield

Bigger. Keep it thin, that is the brand.

Properties
Type layer · Amazing tea!
Transform
PositionX 359Y 83
Character
FontInter
Weight
Size46 pt
Color#FFFFFF
Paragraph
Align
Layers
100%
Creative Review
1Circle 1 · Dana Whitfield
2Box 2 · Marcus Lee
3Arrow 3 · Marcus Lee
4Drawing 4 · Dana Whitfield
TAmazing tea!
TTea «Curtis Bountea» White Chinese tea…
Brightness/Contrast 1
Hue/Saturation 1
Background

Dana wants the headline bigger. It is selected: drag its Size in Properties to about 62 pt, or pull a corner of its box.

One review, both ends·The client's page reads the way the build does; the Photoshop panel is drawn from the Premiere Pro one·Nothing you draw, type or change is saved or sent

Compare versions

Two ways to see what changed.

Swipe

v1 on the left, v2 on the right, the note that asked for the change on top.

Version 1 of a fashion still: a woman with four handbags against a plain studio wall.
Version 2 of the same still, warmed up, blacks lifted and cropped in.
Dana Whitfield · Client Still 04

Can we warm it up and crop in a touch? It reads a little clinical.

Completed in v2
v1v2

What changed in v2·warmer grade·blacks lifted·cropped in 6%

v1:·v2:

Side by side

Version 2 returns to the same link, with version 1 beside it and the previous requests alongside.

Version 1: a woman with her eyes closed tips a white teapot, and steam drifts across a green, daylit garden. The client has circled two things: the steam above the pot, and the leaves behind her.
Version 1·2 open
Version 2: the same photograph cooled to a teal dusk, with blue butterflies flying out of the teapot with the steam.
Version 2·0 open·Ready for the decision
v1:·v2:

III · For the agency

In the loop

Nobody has to ask where a review stands. The relay used to be a person. Now it’s a page.

Both screens work. Pick your seat, then run the review.

Atlassian, State of Teams 2025
IPA and WFA, BetterIdeas Project 2025
IPA and WFA, BetterIdeas Project 2025

One press plays this seat's four moments in the review.

Marcus sends his notes from the client’s link. Press the button under the list and watch who is told.

This is who hears about it.Everyone on the project, and what each one is emailed about.

Truly Being AliveVersion 2 · in review

Feedback sentNotesQuestionQuestionChanges doneDoneSigned offSignedApprovedApproved
Clientby named review link
DWDana WhitfieldClient
MLMarcus LeeClient
Your shop
DEDemo EditorEditor
PNPriya NairCreative director
YouYouProject manager
GOGrace OkaforOwner

Sent by Creative Review
Nothing sent yet

A working sketch of the setup, drawn for this page. Nothing here is saved or sent.

This is what the agency sees.The Preview Workspace: the whole review on one page.

MadAve

Preview Workspace

Truly Being Alive

Version 23 comments
Reviewers
  • Dana WhitfieldFinished · 2
  • Marcus LeeIn progress · 1
Preparing still…A causeway across a bay, from the air
0:02.000 · V2

Marcus LeeNov 11, 2026, 9:42 AM

The whole film plays loud next to our other spots. Bring the mix down about 3 dB so it matches. No more than that, it still has to hit.

Preparing still…The front of a red motorcycle with its headlight on
0:28.500 · V2

Dana WhitfieldNov 11, 2026, 9:18 AM

This is the hero shot of the bike and it sits too far back. Push in so the headlight fills more of the frame, but keep both turn signals in.

Preparing still…A white motorcycle parked on a beach
0:35.417 · V2

Dana WhitfieldNov 11, 2026, 9:21 AM

The beach looks cold next to the shots around it. Warm it up a little. Keep the white on the tank clean, it can’t go cream.

Answered

Warm the whole shot, or only the sand?

Reviewer reply

The whole shot. Just watch the white on the tank.

---End of Review---

How a review ends

The loop doesn't close itself. A person closes it. Then it's closed.

Integrations

Wherever you work, MadAve works. Creative Review connects to the tools your team already runs.

  • Asana
  • monday.com
  • ClickUp
  • HubSpot
  • Salesforce
  • Teamwork.com
  • Slack
  • Yours?
A bright studio: a long wooden worktable with a cup of pencils and a laptop on it, a grey chair and a blue chair pulled up to it, plants, and colourful prints on the far wall.

Built inside a working agency

We ran the relay like everyone else. So we built the fix for ourselves. It worked so well we made it for you.

Fifteen years of making work for brands you know, and a tool used on live projects every week before it was ever a product.

The offer

Start with one real project.

Bring the next review, not the whole agency, and judge it on that one. A tool should earn the second project, not assume it.

30 days free·Card required·$0 today

Independent and Team convert to the standard rate after 30 days unless you cancel. Cancel yourself, any time, with no call required.

The trial has one job

  1. Connect.

    Connect the application and one live client project.

  2. Review.

    Send the proof to a real client reviewer.

  3. Complete.

    Feedback reaches the creative. Version 2 returns. Approval.

Independent.

$49a month, or $490 a year

For the creative who is the agency.

  • One internal user
  • Unlimited clients and reviewers, within fair use
  • Panels for Premiere ProInDesignIllustratorPhotoshopDaVinci ResolveFinal Cut ProPowerPointFigma
  • Guided first-project setup

Team.

$199a month, or $1,990 a year

Most agencies start here.

  • Up to 10 internal users
  • Unlimited clients and reviewers, within fair use
  • Panels for Premiere ProInDesignIllustratorPhotoshopDaVinci ResolveFinal Cut ProPowerPointFigma
  • Guided first-project setup

Enterprise.

Custom quotescoped with you

Compliance and security at scale.

  • More than 10 internal users
  • Full audit trails
  • Enterprise-grade security
  • Dedicated support for large organizations

Creative Review·The launch offerLaunch pricing, from January 1st

Start with one real project.Be first on January 1st.Talk to a person about Enterprise.

Plan

30 days free. Card required at signup, $0 today. Converts to $199 a month after 30 days unless you cancel.Pricing is set. Signup opens January 1st: one email that morning, nothing before it. For organizations with more than 10 internal users, or a compliance team with questions. Tell us the team size and a person replies with a quote. No call unless you want one.

Questions

We already send clients a review link.

A review link collects notes on a web page. Someone still carries them to the person who can act on them. Here the note lands as a marker on the creative's timeline, the creative can ask the client from the panel, and the approval closes the same thread.

What does the client have to install?

Nothing. One link, opened in a browser. They can type a note, speak it, or attach a file.

What does it cost?

Independent is $49 a month, or $490 a year, for one internal user and unlimited clients. Team is $199 a month, or $1,990 a year, for up to 10 internal users. Both start with 30 days free and a card on file: $0 today, and you can cancel yourself any time. Two or three of you? Team is the plan; it covers up to ten. More than 10 users, or a compliance team with questions? Enterprise is a custom quote.

What happens when the client approves?

They press Approved — no changes and put their name on it. The version is marked approved, the editor is emailed, and the project is ready for deliverables.

MadAve

More time to create. Less time to chase.

Start with one real project. Be first on January 1st.
Notes for this prototype
  • Scroll order follows Why, How, What: the cover carries the belief in Jared's words; the relay and the pivot band carry the problem and the idea; How it works is the loop in three steps; then three chapters of product, In the edit (video), On the page (design) and In the loop (the agency's own people); then the decision, the integrations, the origin story, the offer, questions, and a close on the campaign line.
  • The cover art is the illustration you shared. The "Use your own cover art" control swaps it for a still or clip; nothing is uploaded, it stays in your browser.
  • The closing plate is one gesture, in the cover's own language: the cover's hand, printed as a Black man's hand, rests a fingertip on the red circle's anchor point. Where the cover's hands frame a shot, this one places a point. There are no words in it and nothing else on the paper. The circle is a live shape: the two handles on the anchor can be dragged to bend it, and it settles back into a circle when let go; the first time it scrolls into view the handle leans once, to show it is live. The hand is the lower hand from your cover file, cut out, turned, and toned darker with lighter nails; a larger cover file would make it sharper.
  • The wordmark is the real one, cut from the PNGs you shared. Ask the designers for the SVG for crisp edges at small sizes.
  • The feedback loop is the real e. mark, traced from the 2,400-pixel files you supplied (a vector trace, faithful to the pixel). A note travels the brushstroke and draws the mark as it goes, through six stops: 1 Client · One link (the ball terminal), 2 The note on the work (the crossbar), 3 Edits made (the top of the eye; Mark completed), 4 Internal sign-offs (the left side; as many levels as the shop needs), then around the bottom of the e and back up to 5 Back to the client (the ball again, which reads 1·5; the red period appears as the approve button), and 6 Approved — no changes: the period clicks from red to green with a check, and the note turns green with it. The ruler sits in the left column under the headline (under the mark on a phone); it scrubs the loop, the numbered tabs and stops jump to a stop, and it plays once on its own when it scrolls into view, pausing at each stop. The route is hand-set to the glyph, so if the designers change the mark, the route needs re-fitting.
  • "How it works" and "How a review ends" without their graphics (Nov 16; your note: "do you think we need these graphics anymore? be honest... if they should stay"). Gone: the two pills, the small timeline and the green Approved badge above the three steps, and the card with the two decision buttons, a name and a confirmation. They were how this page showed the product before the three pairs of working screens existed. Each had become a small copy of something that works a little further down; the badge and the card still carried the build's older words for the two decisions; the three graphics were three different heights, which left the middle headline 20 px lower than its neighbors; and the card was a picture of buttons under three chapters of buttons that work. Kept: the title, the line under it and the three steps in words; and from "How a review ends" its one line, a sentence to a line. From three columns up the steps share their rows, so their numbers, headlines and words start level even where a headline takes two lines (a tablet). Eye-tracking research (Nielsen Norman Group, "Photos as Web Content") finds that people study pictures that carry information and pass over the ones that only decorate. The page is 264 px shorter in a laptop window and about 740 px shorter on a phone, and about 3 KB lighter as written. The build's older words for the two decisions are now in four places: the note card on the cover, stops 5 and 6 of the loop, one answer under Questions, and the note about the loop above. Choosing one wording for the page is still yours.
  • "In the edit" is now two working screens on one film (Nov 12): what the client sees and what the creative sees, linked. The client's side follows your Nov 12 recordings word for word: the drawing bar (select, circle, square, arrow, pen, undo, redo, delete, Color, Stroke), Screen Shapes, Compare, the player and its controls, Smart Analysis, the version menu and status, Request changes and Approve, FEEDBACK with All, Unresolved and Overall, Edit comment, Delete shape and comment, Overall feedback, Record feedback, Your name, Write feedback and File upload, the "Explain your drawing" box and the "Screen shape and comment posted" notice. The creative's side is the Premiere Pro workspace and panel from your Nov 10 recording, now on real video. A visitor can draw on a frame and watch it land as a red marker, a drawing over the picture and a comment in the panel; make the change; mark it completed; export Version 3; compare versions four ways; line two versions up by their sound; run Smart Analysis; request changes or approve. Nothing is saved or sent.
  • The film in "In the edit" is the one you sent on Nov 12 (Ducati - Truly Being Alive, 61.5 seconds). It plays for real on both screens: picture, sound, exact frames, and meters and a waveform drawn from its own sound. It is somebody's film: it shows the Ducati and Ducati Tampa Bay marks, riders' faces and the dealer's web address, it has music, and the file reads like a download. That is fine for this private prototype. Before the site is public, get the owner's permission in writing or swap the film. Another film can take its place: two scripts make its files, and the four comments, Version 1 and the planted fault are re-aimed at its shots. This film also takes the R Clark construction footage off the page.
  • What is made up in "In the edit": the review itself (Dana Whitfield, Marcus Lee and Demo Editor, their comments and answers, the dates); Version 1, which is Version 2 with two seconds of black at the head, one shot left flat and the web address masked off the end card, so Compare and Audio & sync have something to show; and one fault planted in Version 2, a single black frame at 00:38.958, so Smart Analysis has something to find. The clip names are mine. The colour controls are a simple stand-in for Lumetri, not Adobe's maths.
  • Guesses in "In the edit" for Randy to check, because the recordings did not show them: how a client's drawing sits on the timeline (here a short red graphic on V2 over its frame for as long as its comment is open, kept in a "Creative Review Shapes" bin and owned by the panel, so it cannot be moved or deleted by hand); what the panel shows for a comment with a drawing ("Box on the frame") and for an Overall comment (no timecode, no marker); what a resolved comment looks like on the client's page (a green time and "Resolved"); what Audio & sync shows (here one line saying how far apart the two versions start); what Smart Analysis shows when it finds something (here the time, as a button, and one line); the Stroke and speed choices; the Post button that appears as you type; the question before Approve; the reply box under an editor's question; the wording of the smaller notices; and the Quick tour's five stops, which are mine. New feedback lands on the timeline by itself here so the link between the screens can be seen; in the build the editor presses Refresh Feedback.
  • Held back from "In the edit" until I can see them: the brief (the emailed page with stills, zoom and "ask a question") and "show previous video" in Premiere Pro. Both were described on the Nov 12 call, but the recording's picture had frozen by then. A screen recording or screenshots of each is enough to build from.
  • "In the edit" layouts: from about 1,350 pixels of window the two screens sit side by side, in a block wider than the rest of the page (up to 1,680 pixels). Under that, one screen at a time with a Client and Creative switch, and a red dot on the switch when something lands on the screen you cannot see. On a phone each screen is one column with its picture pinned under the masthead. The five steps and the line under them are the page's guide, not the product's.
  • How "In the edit" loads: nothing of the film is fetched with the page. A thumbnail sheet and the opening frame (147 KB together) come when a visitor is within about a screen and a half. The film (14 MB) and its sound (1 MB) come when they stop at the section for a second, or touch it; on a phone or tablet, on a slow line, or with data saving on, only when they touch it. A small counter shows the percentage. The film is then played from memory, so both screens share one download and every jump is instant. This host holds each file to 15 MB, so the picture is 720p at about 1.8 Mbps; on your own host it can have twice that, or stream from Mux as the product does. The section's markup and styles travel with the page (about 26 KB once the page is compressed); its script (60 KB compressed) is a file of its own, fetched when the section is within three screens. The page itself is lighter than it was in v34.
  • "In the edit" was tested here in Chromium only, by script: exact frames on both screens against frames cut from your file, sound and picture within a frame of each other, every control, the whole review from a drawing to an approved Version 3, a phone with touch, slow lines, the three ways the film can be handed to the players, and the page inside a preview frame like this one. Safari, Firefox and a real iPhone are untested. The H.264 copy of the film that Safari and every iPhone browser get passed the same frame and sound checks in Chromium, with the page told it was Safari and then an iPhone. Safari's rule that only a visitor's own tap may start a sound was imposed on Chromium as well, and the players pass it. That proves the file and the logic, not Apple's browser. Try it by hand on a Mac and an iPhone before launch, and before showing it to anyone on a phone.
  • "On the page" is now two working screens on one ad (Nov 12), built the same way as "In the edit": what the client sees and what the creative sees, linked. The client's side is the review page for a layout. Its drawing bar and comment card follow your Nov 9 screen capture: Select, Pan, Circle, Square, Arrow, Draw, Note pin and Text; undo, redo and delete; zoom; Color with its hex field; Stroke; Size and Edit text for a text mark; Compare and Marks; the plus on each mark that opens "Add a comment · Page 1" with Your name, "Write a comment…", File upload, Discard and Post comment; the name check in the build's own sentence; and the numbered badge once the comment is posted. The capture did not show the rest of that page, so the version menu and its status, Request changes and Approve, FEEDBACK with All, Unresolved and Overall, Edit comment, Delete shape and comment, Overall feedback, Record feedback and Your name are dressed like the video review page in your Nov 12 recordings. The creative's side is a Photoshop workspace with the Creative Review panel. A visitor can mark the ad and watch the mark land on a Creative Review layer with its comment in the panel; make the change in Photoshop (resize or retype the headline, drag the copy until it snaps to the margin guides, lift the tag with a masked adjustment layer, bring the color back with Hue/Saturation); mark it completed; export Version 3; compare versions four ways; request changes or approve. Nothing is saved or sent.
  • The Photoshop panel in "On the page" is a guess: I have not seen it. It is drawn from the Premiere Pro panel in your Nov 10 recording, with "Show / hide layer" from the InDesign words in the Nov 7 walkthrough. For Randy to check: that a client's mark arrives as one layer per open comment in a "Creative Review" group at the top of the layer stack; that Mark Completed takes that layer off, and the client sees the mark turn green with "Resolved"; the panel's wording for a mark ("Comment 1 of 4 · Page 1", "Circle 1 on the page", "4 added · 0 updated · 0 already on the review layer. Save your document."); the three steps of an export; and that new feedback lands by itself here, where the build may want Refresh Feedback pressed. Guesses on the client's page too: "Save text markup" showing only on a text mark's card while its comment is empty (the capture shows that label once) and Post comment, dimmed, on every other mark; what Compare offers for a page (here the four modes of the video Compare); the zoom steps (100, 150, 200 and 300%); and the Quick tour's five stops, which are mine. A screenshot or a short recording of the Photoshop panel is enough to correct all of it.
  • The ad in "On the page" is the Curtis tea ad you supplied, opened into layers so that Photoshop has something real to change. Its headline, copy and web address were taken off the picture and set again as live type in Inter (the page's own face; the ad's own is close to it, not the same), over the photograph, with two adjustment layers: Brightness/Contrast masked to the tag, and Hue/Saturation. With all four changes made, the document is the ad you supplied with its type set again. Version 2, in review when a visitor arrives, is an earlier round made here from it: a smaller headline, the copy low in the corner, the tag in shadow, the color pulled back. Version 1 is an earlier one still. The four comments, the limits in them, the designer's questions and the answers are invented. It is another brand's ad with a gallery site's mark in the corner: a stand-in. Before launch, swap in your own layered file or get permission, because on this page it reads as a client of yours.
  • What the Photoshop screen in "On the page" is and is not: a working stand-in built here, with no Adobe artwork and no Adobe logo in it. It has five tools (Move, Type, Eyedropper, Hand, Zoom), two type layers, two adjustment layers and a locked background. Layers can be selected, hidden and faded, not added or deleted. Brightness/Contrast and Hue/Saturation are simple stand-ins for Adobe's maths. The margin guides and the snapping are there because the second comment is about a margin.
  • "On the page" layouts and loading: the same breakpoints as "In the edit". Two screens side by side from about 1,350 pixels of window, one at a time under that, one column each on a phone, where Photoshop keeps its document pinned under the masthead with the tools laid over it and Review, Properties and Layers as tabs. Photoshop shows its document, the panel, and Properties over Layers when it has about 1,000 pixels to itself; narrower, the panel and Properties take turns in one frame with Layers under them. The section's markup and styles travel with the page (about 17 KB once the page is compressed) and already show the first state of both screens before any script runs. Its script (56 KB compressed) and the photograph (160 KB) are fetched when the section is within three screens or is touched. The headline's weight of Inter is one small font request more, made by the section itself.
  • "On the page" was tested here in Chromium only, by script: the whole review from a circle on the ad to an approved Version 3, by mouse and by touch; every tool on both screens; undo and redo on both; the limits in the four comments; versions and Compare; sizes from 320 to 1,920 pixels with and without scrollbars; the keyboard; reduced motion; the page before its script arrives; each of its files missing for a moment, for good, and kept as "not there" by the browser; the photograph arriving three different ways, including one where the browser will not let the page read its pixels; six content security policies; and the page inside a preview frame like this one. Version 3, made by hand from Version 2, comes out within about one level in 255 of the finished layered document. That document and the ad you supplied are the same photograph to within half a level on average; the headline and copy are set again in another face, so there the two differ. Safari, Firefox and a real iPhone are untested: try it by hand before launch.
  • Holding still (v36): three fixes so that what a visitor is looking at does not move. The line above each pair of screens now keeps one height at each window width whatever it says, under "In the edit" as well, so the screens under it do not shift when its sentence changes. On a phone that leaves a little air around a short sentence. Picking a text mark on the ad adds two controls to the tool bar, which can take it onto another row: the ad now stays under the pointer when it does. And the screens under "In the edit" grow when their script arrives, by 330 pixels in a wide window and by 500 to 670 on a phone. Chromium holds the page under them still by itself. Safari may not, and then a visitor who used the masthead's link to "On the page" would be pushed down the page by that much a moment after arriving. The page now holds itself still where the browser does not. Tested in Chromium with its own scroll anchoring turned off, which is the nearest thing to Safari available here. Not tested in Safari.
  • Loading, made sturdy (v38): on Nov 13 these screens came up with the browser's broken-picture mark where the ad should be, a blur behind it on one side and an empty frame on the other, and a line saying the two screens had not loaded. The three files that were new in v36 had not arrived, and the page asked for each of them once. What changed, under "In the edit" as well: a picture on these screens is shown only once it has arrived, so that mark is never drawn, and until then the same soft blur stands in on both screens. A file that does not arrive is asked for again by itself: after 1.5, 4, 10 and 20 seconds, then more and more slowly for about an hour, and at once when the visitor comes back to the tab or touches the screens. Every later request goes past anything the browser kept from the one that failed. While that goes on, the line above the screens says "Loading the two screens…"; after five tries it says they did not load and offers a Try again button. The photograph under Photoshop's layers is asked for the same way, and says so in both lines if it does not come. The ad's two picture files have new names (tea-plate and tea-v2): the old ones began with "ad-", which a content blocker can take for an advertisement. Why the files were missing on Nov 13 is not known for certain. The likeliest cause is that the page was open in a tab while v36 went out, and asked for the new files a moment before they were being served.
  • The fashion still (compare) and the teapot pair (versions) are demo pieces. The teapot pair is the before-and-after you supplied on Nov 10, cut into its two halves. The file is small, 361 by 418 pixels a half, so each half was cleaned of its compression marks and doubled with an enlarger built here for the job, and the two frames are held to 361 pixels wide: the size at which a retina screen shows the result pixel for pixel. It cannot run larger without going soft. For full-size frames it needs the original files, about 1,100 pixels wide a version or more. The tea (Butterfly Hour), the two requests beside the pair and the designer's question are invented here to fit what changed between the versions; check the name before it goes public. Clear the rights and the people's OK before anything goes public; v2 of the fashion still is a quick grade done here.
  • The Panels bar and the price cards show eight apps: Premiere Pro, InDesign, Illustrator, Photoshop and DaVinci Resolve, and, added Nov 10, Final Cut Pro, PowerPoint and Figma. All eight icons are the files you supplied, fitted to a square and otherwise untouched (Resolve's checkerboard keyed out). Their use on the live site falls under Adobe's, Blackmagic's, Apple's, Microsoft's and Figma's brand guidelines. The relay cards use the Gmail, Slack, Asana, Drive and Teams logos you supplied (Google, Slack, Asana and Microsoft brand guidelines apply). The deck's rule was validated tools only, so every app on the bar should have a working panel by launch.
  • The Integrations band is new (Nov 10): the seven tools you named, each with the logo you supplied. It first sat below Questions; it now follows "How a review ends," ahead of "Who's behind it" and the offer, so a visitor learns the product fits their tools before reaching the price. The checkerboard backgrounds were taken off the HubSpot and Salesforce files, and the off-white square and its frame off the Teamwork.com file; each logo is fitted to the same box, and nothing in a logo was redrawn. Six are symbols; Teamwork.com's is the stacked wordmark you sent. The names are spelled the way each brand spells its own (monday.com, ClickUp, HubSpot, Salesforce, Teamwork.com). The band says only that Creative Review connects to these tools, not what each connection does: that copy needs you or Randy. The "Tell us" field answers on the page and sends nothing; in production it should reach a person, and may want an email beside the tool's name. Check each brand's partner and logo rules before launch.
  • The picture beside "Built inside a working agency" is the office photograph you sent on Nov 10; it replaces the "Photo to come" box. The file is 740 by 415 pixels, so it was doubled with the enlarger built here for the teapot pair, and its frame never runs wider than 740 pixels. The section is tighter too: the picture is less than half as tall as the old box, and there is less space above and below it. Where the picture came from was not stated. Under this heading a visitor will take it for your own room, so check that its licence covers the site, or swap in a photograph of your space when there is one.
  • "Your numbers, not ours" is live and says so: each figure has a slider and can be typed over (the pencil and the "Drag, or type your own" tag), the total ticks as it changes, and "Back to 6 × $60 × 52" resets it. Beside it, the same numbers are drawn as one year of 52 working weeks, red for the weeks the relay takes (hours × weeks ÷ a 40-hour week). When the card first scrolls into view the hours slide up to 9 and back once, to show it is live. Defaults are the sheet's (6 hours × $60 × 52 = $18,720). The 57% line is the Monotype & Extensis source, used to say six hours is conservative.
  • Pricing (Nov 9): Independent $49 a month or $490 a year, one internal user; Team $199 a month or $1,990 a year, up to 10; Enterprise is a custom quote (compliance and security at scale: audit trails, enterprise-grade security, dedicated support). Founding teams came off on Nov 9. Both paid plans: 30 days free with a card, $0 today, self-service cancellation. The plan buttons pre-fill the one form; Enterprise switches it into quote mode. The Enterprise bullets need to be true at launch.
  • Reviewer names on the page (Dana Whitfield, Marcus Lee, Demo Editor, Demo Designer) are placeholders.
  • "In the loop" is new (Nov 14): chapter III, for the agency's own people, built as two working screens like the two chapters above it. On the right is the Preview Workspace on a phone, following your Nov 13 screen recording word for word: Reviewers with In progress and Finished, the All reviewers menu and Awaiting answer, a card for each comment with its still, EXPAND with Zoom in and Fit still, Play from comment with the two frame buttons and Back to comment time, Awaiting answer, Answered and Reviewer reply, Preparing still, and the End of Review line. It is the same review as "In the edit": Truly Being Alive, Version 2, the same four notes from Dana and Marcus, on the Ducati film. Four things differ from the recording, on purpose: the line over the title says Preview Workspace where the build says Review Brief · Private demo; the line about a missing reviewer email is left out, because these two reviewers came by named links; the stills carry no drawings, because the recording showed none; and the frame buttons wake once the film has played for a moment, when the note beside them goes.
  • The left screen under "In the loop", who hears about what, has not been seen. It is this page's own picture of what you described: everyone on the project on one list, who is emailed and when, and triggers that move as decisions are made and work is done. Its five moments come from what the page already says elsewhere: feedback sent, a question asked or answered, the changes done, the sign-offs, approval. Four guesses in it need Randy: that a question is emailed to the reviewer who wrote the note; that whoever signs off next is emailed when the changes are done; that the last sign-off emails the client the new version; and the three setups (Owner-led, CD signs off, Two sign-offs), which are examples of how shops run, not templates known to be in the product. The names on the list are placeholders. A screenshot of the real setup screen is enough to redraw this side to match.
  • Why three seats, three short tours and a cited figure on each card. Research on product tours (Navattic, 2026) finds that several short tours a viewer chooses between are finished more often than one long one (57% against 35%), that the best-finished tours run one to six steps, and that the best ones sit in the open with no form in front of them. Software like this is bought by a group of three or four (G2, 2025), and here that is the owner, the creative director and the project manager. The figures on the cards are from Atlassian's State of Teams 2025 (a quarter of a team's time goes to searching for answers) and from the BetterIdeas Project by the IPA and the WFA, 2025 (23% of agencies say the approval process works well; 43% say the right people sign off). Each card links to its source.
  • What "In the loop" costs to load: about 11 KB more page as sent, and a script of 17 KB as sent that is fetched when a visitor nears the section, like the two above. Four small stills (about 95 KB together) come with it; the large ones come when a still is expanded. The phone plays the film from a copy of its own, 640 × 360 with its sound (about 4.5 MB), fetched only when Play from comment is pressed.
  • Compare and Versions, side by side share one row since Nov 14, each about half the size it was: with their headings, about 820 px of page at a 1,440 px window where the two took about 1,700, and about 1,430 px on a 390 px phone where they took about 2,030. Nothing was taken out. The two lines that introduced them now sit over each one, word for word, and every picture, note, request and Use your frame control is still there. On a phone the two versions stay next to each other.
  • "In the loop" and the compare row were tested by script in Chromium: 662 checks, all passing: every moment of the review and who is emailed at it; the envelopes, the three setups and added people; both filters on the phone; the three tours, step by step and by hand; the still and the film (the start frame, the frame steps, the sound, a host that serves no byte ranges, a film that does not come); 23 window widths from 320 to 1,920 px; the first frame against the working screens; a script or a still that does not come; calm motion; the keyboard; scripts off; and the page as staged for the host, by real presses. Every other part of the page was compared with v38 at five widths, picture by picture and box by box: identical outside the two navigations and these notes. Both older suites were run again on this page: 543 and 210 checks, all passing. Not tested: the real host, a real Safari, Firefox, and a real iPhone or iPad.
  • Watch the review: one press (Nov 14; your note: "the button needs to be more visible with a more clear this is what's happening and Why", "I am leaning that it should [be one click] so they don't stop by accident", "maybe it should light up or the button should flash"). Each pair of screens now has one red button above its steps: Watch the review, 1 min (Watch this tour, 20 sec, under "In the loop"). It glows three slow times when it first comes into view, then rests. One press plays the whole review in six parts, about a minute, and a bar at the foot of the window says for each part whose screen it is on, what is happening and why it matters, with Pause beside it. What the research said: no study tests autoplay against click-through head to head, but every step a viewer has to press loses some of them (Navattic, 40,000 demos: the best completion at 1 to 6 steps; Arcade, 14 million sessions: a drop at step 7), a demo shown in parts is understood better even when it sets its own pace, and a Pause that is there helps even when it is hardly pressed. A short glow is effective and allowed as long as it stops inside five seconds (Nielsen Norman Group; WCAG). Nothing ends it by accident: scrolling never does, and since v45 scrolling for a better look does not pause it either (on a phone a finger that scrolls on the screens is a scroll, not a press), a press elsewhere on the page is ignored, and a press on the screens only pauses it for the visitor's turn, with Resume picking up from wherever they leave the review. While the visitor scrolls, the pointer, its red outline and its words stay on the control they are on. Under "In the loop" the same button then offers the next seat and plays it. Left out of the film on purpose: Smart Analysis (on Version 3 it flags a flash frame, and a client approving in the next breath would make no sense). The captions are written for this version, in the page's own voice, and are easy to change.
  • Squared up on the screens (Nov 15; your note: "When you click can it automatically square your screen up to see better? Mine was not lining up and when I scrolled for better framing it paused the demo"). One press on Watch the review now brings the two screens to the top of the window first, their top edge just under the masthead, and only then does the pointer set off. In v44 the words and steps above the screens kept the upper half of a laptop's window, and the screens sat half out of it. Measured in the window of a 13 inch laptop (1440 by 790), between the press and the end: "In the edit" now moves the page twice (v44: seven times), "On the page" four times (v44: nine), and a tour of "In the loop" two or three times (v44: three to five). While it plays, the page stays where it is for as long as the next control is in sight. When it has to move, one move serves the controls that come next, and it comes to rest on the screens' top edge or on a screen's lower edge where one of those is near. Scrolling for a better look no longer pauses it: nothing is pulled from under your hand while you scroll, and when you stop it goes on from where you have left the page, bringing the screens back into place first if its next control is out of sight. If you scroll away to something else, so that the screens no longer fill most of the window, it does not pull you back: it waits, says so on the bar, and goes on by itself when you scroll back to the screens (Resume brings you back too). Scrolled right out of the window, it is still put away, and the button offers the rest. When it ends, the page goes back to the line you pressed on, as before. In windows under 1,180 px (tablets, phones) it opens on the screens the same way and then brings each control into view by the least scroll, as in v44. Show me this step is no longer ended by a scroll that keeps its screens in the window.
  • Show me this step (the v42 button, kept; your note then: "let's demo this better show them what to click"). It sits beside the guide's line as a quiet outline, for a visitor doing the review by hand who wants one step shown: a pointer goes to each control the step uses, lights it, says in a few words what it is about to do, presses, drags or types, and the step happens. It shows everything the film shows, and Smart Analysis, the client's answer typed on the client's page, and Compare side by side as well. What it shows is Creative Review. Premiere's and Photoshop's own controls are touched only where a comment's change needs one, and then only that one: Level to −3, Scale to 108, the copy's X and Y. It follows the film's rules: scrolling and a press elsewhere on the page do not end it; a press on the screens does. On a touch screen the pointer is a fingertip, and with reduced motion it does not travel. The comments it types ("This corner goes muddy…", "The cup looks cold…") and the name it signs with (Dana Whitfield) are placeholders, like the rest of the review.
  • Watch the review and Show me this step were tested by script in Chromium: each film from one real press, on a desktop with both screens, with one screen at a time, on a tablet, on a phone, on a phone held sideways, in short laptop windows (down to 1,280 by 620) and with reduced motion: every caption word for word, in order, and up at least as long as it takes to read; what the pointer pressed, in order; where the review stood at the end; the length; that the pointer's tip stood on every control it pressed, with nothing over it, inside the window and clear of the bar. Since v45, in four windows from 1,280 by 680 to 1,920 by 970 and on a phone: that one press brings the screens' top edge to rest 10 px under the masthead before anything is pressed; that the words above the screens do not come back into the window until the film ends; how often the page moves; and that it is back on the visitor's line at the end. Pause, Resume, Stop, Watch the rest and Watch again, from the button, the bar and the keyboard. A visitor who scrolls while it plays (the wheel, a finger, the scrollbar, and a page moved with none of those to be heard), who keeps scrolling across the moment the film needs the page, who scrolls right away from the screens and comes back, who pauses and looks around, who scrolls the Preview Workspace's own page, who taps the screens or presses a key on them: the film goes on, waits for them to stop, waits for them to come back or hands over, as described above; scrolling for a better look never pauses it; nothing is left floating; and the page holds still under a hand that has pressed Pause or the screens. A press before the section's script has arrived; the button's glow; the guide at eight widths, with nothing moving when a label changes; and the page as staged for the host, with no test hook. The numbers are in the project's notes (madave-io-homepage-notes.md). Pictures were looked at as well as counted: the frame the page opens on and every frame it came to rest in, in a 13 inch laptop's window, and every paused state on a desktop and a phone. Not tested: the real host, a real Safari, Firefox, and a real iPhone or iPad, where the bar's place above the browser's own toolbar, a thumb on Pause and the on-screen keyboard staying down matter most.
  • The form is not wired; every button on the page lands on it. In production the trial button goes to signup with the card step.
  • Affiliates, LinkedIn, Instagram and Facebook (Nov 16; your notes: "Can we add the affiliate page to link at the top and bottom of the website" and, on seeing it in the bar, "Let's move this link maybe after questions in the header"). Top: from 1,101 px of window "Affiliates" is the last link in the header's row, after Questions. Under that it stands at the right end of the bar above the nameplate: the row is not shown under 900 px, so a phone or a tablet would otherwise have no link at the top, and up to 1,036 px eight links do not fit the row on one line. Under 360 px the bar drops "No. 01" to leave the link room. The bar's middle phrase sits centered over the wordmark from 880 px. Bottom: "Affiliates" is in the footer's links, before "Top", and the two stay together when the links wrap. For now all three open the affiliate page's design, which is a separate prototype with its own link: anyone you share this page with needs that one shared too. On the live site they go to madave.io/affiliates, in the same tab. LinkedIn, Instagram and Facebook in the footer were plain words; they are links to the three pages you sent. From tablet width up they sit at the right of the copyright line, because with "Affiliates" added the links fill the first row. Usability research (Nielsen Norman Group, "Web Page Footers 101") puts links for a site's other audiences and the company's social accounts in the footer, which people scroll to on purpose to find them.