Exaflair design context

What we stole from wisprflow.ai, translated

Source: wisprflow.ai, dissected 2026-09-09. The rule is the same as the adko round: every move below is built for real as an Exaflair section, in Montserrat, on a white ground, with the brand's orange as surfaces. Under each one a small plate says what the move is, where it came from, and what changed. Numbered so you can point at them.

Moves 1 and 2 Nav card, pivot headline

Exaflair, product engineering studio

Plug in the team, not the overhead.

Product minds, AI-boosted builders and systems that scale. You get working software every week and the estimate is attached to a prototype, not a deck.

Powered by intelligence, driven by flair.

Start a project How we work

Teams of two to twelve. Weekly demos. Fixed-price discovery.

Move 3 Before / with, one reveal step

A deck first, or a prototype first

The usual proposal

40 pages

of deck and estimate before anyone touches a screen.

An Exaflair proposal

2 weeks

to a working prototype you can click through, with the estimate attached to it.

Move 4 Sticky device, step rail

How we work

Working software, every Friday.

  1. Step 1

    Discovery in the open

    Two weeks, fixed price. We map the product with your team on a shared board, cut it to a first slice, and write the estimate against that slice. You keep the board either way.

  2. Step 2

    Prototype before estimate

    The proposal is a clickable prototype with the numbers next to it. Arguing from a screen is faster than arguing from a slide, and it exposes the hard part early.

  3. Step 3

    Build in weekly slices

    Every Friday there is a demo of running software, not a status report. Scope moves in slices you can see, so the plan and the product never drift apart.

  4. Step 4

    Hand over, stay on call

    You own the repository, the infrastructure and the docs from day one. After launch we stay on a short retainer while your team takes the wheel.

Move 5 Rounded band edges, the one takeover

Quintillion scale. Finesse built in.

Exa brings the scale of a quintillion. Flair adds the finesse, with intelligence built in. This gradient appears once on the page as a field; this is it, and it rises over the white as a plate rather than cutting it as a stripe.

See the work

Move 6 Colour plates on white

Selected work

Three builds, told in numbers.

FintechSector placeholder until logo permission

Fifteen onboarding fields became seven, and the last screen proves the first six worked.
157fields, one flow
1shared state carried into the recap
Open the case

HealthtechSector placeholder until logo permission

A voice-first coaching app argued as a spec sheet, with the screens working beside the argument.
4screens, one living prototype
2themes, both verified at 4.5:1
Open the case

Supply chainSector placeholder until logo permission

Trade documents told as they move: who signs, what changes, what the system checks.
3rounds to approval
1accent, the client's, as a thin rule
Open the case

Move 7 Chat-shaped FAQ

Questions

Fair questions.

Questions

Answer

Who actually does the work?

Exaflair studio

A named team of two to twelve: a product lead, designers and engineers who stay on your project from discovery to handover. Nobody is swapped in mid-build without your say, and you meet everyone before we start.
How do you price a project?

Exaflair studio

Discovery is a fixed price for two weeks. The build is quoted per slice against the prototype, so the number is tied to screens you have clicked through. Retainers after launch are monthly and cancellable.
Where does the AI come in?

Exaflair studio

In the workflow, not as a substitute for the team. Builders use AI tooling for scaffolding, tests and review so more of the week goes to the hard parts. Where the product itself needs a model, we design that as a feature with its own evaluation, not as a demo.
Do we own the code?

Exaflair studio

Yes, from the first commit. Repositories, cloud accounts and design files sit in your organisation; we work inside them. When the engagement ends there is nothing to transfer.
What happens after launch?

Exaflair studio

A short retainer while your team takes over: on-call fixes, a written handover, and pairing sessions with whoever inherits the code. Most teams run it for one to three months.
How soon can you start?

Exaflair studio

Discovery usually starts within two weeks of a first call. We reply to every enquiry within two working days with a yes, a no, or a date.

Question 1 of 6

Move 8 Gradient CTA card, static

Start a project

Start with a prototype.

Two weeks of discovery, one working prototype, and an estimate attached to it.

Book a discovery call See the work

We reply within two working days. Discovery is fixed price.

Left on the table Not translated

What wisprflow.ai does that Exaflair does not

Each item is a real strength or habit of the source. It stays there because it conflicts with a brand rule, a taste note, or the craft floor the playbook already enforces.

  • Cream and beige grounds #FFFFEB / #E4E4D0

    Sri Pardhiv rejected cream and apricot grounds as "brown" in round 3. Exaflair stays on white and #F1F1F1.

  • Dark section grounds ~37% of the page height

    Near-black and dark-green bands contradict white grounds. Dark appears here only inside components: the FAQ question pane, the buttons, the legal bar.

  • EB Garamond display a second family

    The brand is Montserrat only. The pivot is reproduced with weight and italic, not a serif.

  • Lilac CTA and 2 px black borders on every button #F0D7FF

    Exaflair's CTA is Almost Black (or Yellow Orange with an Almost Black label). Borders stay on the outlined variant only.

  • 6,011 px pinned morph and 3,085 px scrubbed testimonial pile GSAP ScrollTrigger

    Both exceed "scroll-reveal at most" and neither has a reduced-motion fallback. Here: one reveal step and a straightening rotation, both off under reduced motion.

  • Continuous ribbons and marquees text-on-path, 40 s logo ticker, three transcript marquees

    Perpetual motion. The Exaflair logo strip stays the adko hairline strip, static; the hero fills with the proof card instead of ribbons.

  • Motion-blurred lifestyle photos as product surfaces

    Right for a consumer dictation app, off for a product-engineering studio. Here: product screens on gradient and grey plates.

  • Coral and mint accents #FF6C4C / #34D399

    Outside the brand. The client's colour is the only permitted second accent, as a thin rule.

  • The craft floor 57 empty alts, 43 of 51 targets under 44 px, 13 px button labels, 3.3:1 rail text, 4 console errors, a localhost script in production, 2.2 MB of tag manager

    Exaflair's playbook already requires 4.5:1, 44 px, zero console errors and alt on every meaningful image; this page is checked against all four.

  • Giant wordmark footer 756 x 264 "Flow"

    adko had it too, and it was in the adko steal list, but PR #7 dropped it on Bhavya's note. Two references for, one client decision against: left out unless he re-raises it.

Contradicts adko and Bhavya's notes

Where wisprflow.ai disagrees with the adko steal list or with Bhavya's notes, and who wins

  • Ground strategy dark blocks vs white

    wisprflow: cream ground, 27% near-black, 10% dark green. Bhavya and Sri: white or light grey only. Bhavya wins; the plates are kept, the grounds are not.

  • Colour rationing 0 to 1 moments, then 4 to 5

    wisprflow rations to one lilac for 80% of the scroll then releases five plates at once: the "too quiet" then "too bold" failure modes Bhavya named. Spread instead: gradient proof card, plate trio, gradient CTA, so every viewport lands at 2 to 3.

  • Sparse hero ~60% empty at 1440

    Bhavya wants "effortless yet full". The proof pair sits inside the first viewport under the hero copy.

  • Display voice serif sentence case vs Anton 900 uppercase

    Both are editorial scale (96 px over 17 to 20 px), opposite temperatures. Middle path: Montserrat 800 upright + 400 italic pivot in sentence case everywhere, 900 uppercase kept for the one band.

  • Set pieces pinned 6,011 px, scrubbed 3,085 px

    adko and wisprflow agree with each other and disagree with Bhavya's "a tad less motion". Bhavya wins: scroll-reveal at most.

  • Wordmark footer

    Two references for (adko, wisprflow), one client decision against (PR #7). Left out; wisprflow is evidence it is a common Webflow-era pattern, not a differentiator.

  • Entrance animation wisprflow: none

    wisprflow's hero is pixel-identical at t=0 and t=2 s. It agrees with Bhavya and goes further than adko. Adopted as a rule: no load choreography on Exaflair pages; this hero has none.

  • Video 0 vs adko's 31 autoplay loops

    wisprflow proves a full product site on 0.9 MB of images. Supports the adko leave.

  • Type units rem tokens vs adko's 1vw body

    wisprflow's rem-per-breakpoint type supports the adko leave; its 13 px mobile button label and 1.3 body line-height sit below the Exaflair floor (16 px UI text, 1.45 to 1.55 body).

  • Reduced motion neither reference honours it

    Zero prefers-reduced-motion rules on wisprflow, 104 tweens still registered under it. Exaflair keeps the rule; every state on this page is complete with motion off.

  • Contrast 3.3:1 rail text vs the 4.5:1 floor

    wisprflow's black-on-warm-plate pattern (6.2 to 9.1:1) is the proof that orange plates with Almost Black type are the right way to use orange as a surface, the opposite of white on Tangerine. Its 50% black rail text is the one thing that fails, and is fixed here.