Guiding Elephant is a finance consulting firm whose advice was ahead of its website. We shipped a ten-page, single-author Framer site in 2024: a full identity system matched to the firm's credibility, an efficient CMS the team could run without us, and a deliberate refusal to build it in custom code. The platform call, not the design, was the decision that mattered most.
The brief was not "build us a nice site." It was "make the site match the advice." A finance consultancy sells judgment. If the site looks thinner than the counsel behind it, a prospect discounts the counsel before the first call.
What was actually broken?
Not the firm's expertise — the gap between it and what a prospect saw online. No site, no identity system, nothing that signaled the depth of the advice being given. A consultant selling financial judgment cannot afford to look like a hobby project, and the prior state read as one.
We did not start with pages. We started with the identity: a brand system built to carry the weight of "trust us with this decision," then a ten-page structure — home, services, team, and a handful of supporting pages — built to hold it.
Why Framer, and not a custom build or WordPress?
Because the job the site had to do fit Framer's strengths exactly, and every other option would have paid for capability nobody asked for.
Ten pages. One author. A design language that wanted room to breathe — expressive layout, custom motion, a look that reads as considered rather than templated. That is the Framer case, not the WordPress case or the Webflow case. We've written the full decision tree elsewhere: Framer wins on design-led, low-content-volume, single-editor sites; it loses the moment content volume or structured data goes up. Guiding Elephant never crossed that line, so we didn't build past it.
The platform decision in one table:
| Signal | Guiding Elephant | Would have pushed to Webflow/WordPress |
|---|---|---|
| Page count | 10 | 20+ |
| Editors | 1 | 3+ |
| Content type | Marketing, mostly static | Blog, case library, e-commerce |
| Design bar | High, expressive | Templated is fine |
Every row landed on the Framer side. A custom-coded stack would have added weeks of engineering for design flexibility Framer already gives out of the box, for a client who was never going to need headless CMS queries or e-commerce logic.
What did the CMS decision actually solve?
The team needed to update services copy and team bios without opening a ticket with us. That's the whole requirement — not a blog, not a content library, not multi-language. We scoped a CMS sized to that requirement inside Framer's own content model instead of reaching for a headless setup that would have needed its own hosting, its own auth, and its own maintenance conversation.
The refusal here was the same one that shows up on every build: don't build the CMS the client might grow into, build the one the team can run on day one. If Guiding Elephant's content needs outgrow Framer's model, that's a real conversation to have later, priced against what's actually needed then — not a hypothetical to architect around now.
What did the identity system have to prove?
That the firm's depth was visible before a prospect read a word of copy. A finance consultancy's site is a credibility instrument first and an information source second. We built the identity to match the register of the advice: no template gloss, no generic "trusted advisor" visual language — a system specific enough that it could only belong to this firm.
The team pages carry more design weight than is typical for a services site. That was deliberate. Prospects vetting a consultancy look at who is giving the advice before they look at the service list.
What would we do differently?
Push the CMS-scoping conversation earlier in the timeline. It landed right — the team runs the site without us today — but we settled the content model after the page structure was mostly locked, which meant one late pass to fit the CMS fields to pages that weren't originally built around them. On a ten-page site the cost was a day, not a rebuild. On a larger one, that ordering mistake gets expensive fast.
The platform call — Framer, not a custom build — was right the first time. Ten pages, one editor, a design bar that mattered more than content depth: that's the profile every time, and we'd make the same call again without a second look.
The instinct behind that platform call — matching the tool to what the brief actually requires, not to what's most impressive — is the same one behind how we scope every build before a line of code gets written.
Written 2026-08-14 by Naman Barkiya.