Adia Grid InsightsFour directions · one record
Bring order to
your tech execution.
Four complete website directions for Adia Grid Insights, fractional
operations and technology leadership for founder-led MSME tech companies. All four
are built from a single transcription of the live site, so every service, testimonial,
FAQ, statistic and contact detail is identical across them. What changes is the
argument each one makes.
Source adiagridinsights.com
Facts build/data.py
Services 5 cards, 3 lines
FAQ 10
Testimonials 3
01 — PRECISION
The drawing set
A ruled working document, not a brochure about one.
A diazo-blueprint sheet set under a live quadrille grid, where the claim to
bring order to execution is performed by the material instead of asserted in a
headline. Five services are five numbered sheets in a drawing set; the 60–90 day
engagement is a real dimension line measured against the 90-day rule; the ten FAQs
are a numbered query register on inverted vellum.
- Skill
- impeccable
- Motion
- Lenis + GSAP ScrollTrigger, one hand-rolled canvas
- Refuses
- The dark-navy consulting page and its cream-editorial opposite
Open direction 01
02 — SIGNAL
The operating system
What a well-run SaaS company's own site looks like.
Swiss Modernism 2.0 on a bento card vocabulary: a real token layer, one
component reused seventeen times, and the same disclosure element serving both the
five service cards and the ten FAQ rows. The five cards are grouped under their
three published service lines, so the repeated names read as two angles on one
line rather than a copy-paste error.
- Skill
- ui-ux-pro-max
- Motion
- Zero libraries — CSS plus one IntersectionObserver
- Refuses
- Fake charts. The KPI strip shows only published numbers
Open direction 02
03 — GRIDWORLD
The field resolving
Chaos becomes an operating system, literally.
One scroll-driven Three.js world across eight chapters. The same 1,440 work
units are the mess, the grid and the logo: each owns a tumbling chaos pose, a slot
on the lit plate, and a cell of the standing diamond mark. Camera, fog, light and
colour all read off one fractional chapter number tied to native scroll. Hovering
or keyboard-focusing a service lights its fifth of the grid.
- Skill
- build-threejs-scroll-worlds
- Motion
- Three.js and nothing else. 5–7 draw calls, ~34k triangles
- Refuses
- Model files, texture files, images. All geometry is generated
Open direction 03
04 — SYSTEMS
The spec sheet
Built out of the discipline it sells.
Near-black and bone with one acid-lime accent that only ever marks what
matters. Hard rectangles, zero radius, hairline column rules, every block
numbered the way a spec sheet is numbered. The four published pillars become
01–04, the five services 01–05, and the stat band carries exactly the four
figures the client publishes — because there are exactly four.
- Skill
- hallmark — design study of a reference the client chose
- Motion
- Zero libraries. One CSS marquee, one scroll-driven rule
- Refuses
- The logo wall, the invented stats, the tool chips
Open direction 04
What none of them do
The live site publishes no address, no hours, no founder name, no founding year,
no pricing and no social links. All six stay None in
build/data.py and every builder omits the element rather than filling
the gap. No direction invents a statistic, a client logo or a review.
The live contact form POSTs to a third-party endpoint we do not own. No direction
carries it over; each falls back to the published phone and email.
The five photographs on the live site are AI-generated marketing renders carrying
burned-in wall slogans and a corner watermark. Direction 02 crops and duotones one of
them so both artefacts fall outside the frame; directions 01, 03 and 04 use none of
them at all.
Direction 04 is modelled on a reference site the client pointed at. That page leans
on a wall of eleven named client brands and on figures like “200+ deployed”
and “98% satisfaction”. Adia Grid Insights publishes none of them, so
direction 04 takes the visual language and refuses the proof: its gate fails the build
on any word the client never published.
Direction 03 loads a Three.js module from a CDN, so it needs to be served over
HTTP — Chrome blocks ES-module imports from a file:// origin, and the page
will silently stay in its static fallback if you open it from disk.