Framer Website · Enterprise AI · Warsaw
Their website still described the company they used to be.
WeAreFuture is an AI consultancy. Their site sold training. Five pages, two languages, and the first enquiry landed six hours after launch.
Context
An AI consultancy that had outgrown its own website.
WeAreFuture is a Warsaw AI consultancy: implementation, advisory, training, and their own AI System product. A Microsoft Solutions Partner, working with enterprises including AbbVie, Henkel and PZU.
They found me through my Framer Experts profile in January. The brief was narrow: a Figma file existed, the homepage needed building, roughly one-to-one.
Problem
The site sold training. The company had moved on.
“Time is against us - our site only talks about training right now, and we’re expanding well beyond that.”
One of the founders, in the second week
Prospects arriving from a sales conversation found a page describing a smaller, different business - one that ran courses, not one that implements AI inside enterprises.
Two things made this harder than a straight build. The material arrived in pieces, over weeks, while the company kept moving: copy was rewritten mid-build, subpages were designed as we went, and type sizes drifted between files. And the deadline was not negotiable - they were already in conversations where the site had to exist.
Decisions
Five calls that changed the outcome.
Hired to implement. Ended up designing.
The engagement started as production work: take the Figma, build it in Framer. What arrived was inconsistent in the way handoffs usually are - the same heading at 22px on one page and 24px on another, body text at 14, 16 and 20, spacing that never repeated. Rather than reproduce that faithfully, I built a style library and put everything on one scale. When the training page turned out to need design rather than implementation, I took it instead of sending it back into the queue. A one-to-one implementation job ended as five pages, two languages, a blog, and a design system holding them together.
The motif that carried desktop was crowding the phone.
The brand’s diamond motif did real work on desktop. On a phone it took the space the first sentence needed, and a third of their traffic is mobile. I scaled the shapes back, made the sections sticky so colour and content changed in place, and moved the long stacks into accordions with a progress indicator. The brand stayed. The scrolling stopped feeling endless.
Every enquiry had to say where it came from
The site was built around a HubSpot pop-up on every call to action - but the useful part is the mapping underneath it. Each page passes its own hidden fields, so an enquiry arrives tagged with the subpage that produced it. That’s the difference between knowing the site gets traffic and knowing which page closed the gap. It’s also why the result below is a fact rather than an impression.
Findable by machines, not just people
An AI consultancy that AI systems cannot read is an awkward position to be in. Beyond the usual - sitemap, alt and aria labels across two dozen client logos, structured data - I implemented llms.txt in both languages, in March 2026, before most sites had heard of it. The FAQ schema was the stubborn part: Search Console kept rejecting it and refused to refresh whatever we changed. I wrote a patch script, pushed it, and it validated.
Two languages, clean URLs
The English version was not a translation layer bolted on top. Five pages were rebuilt in English with their own SEO-clean URLs, plus a custom language switcher that swaps the page rather than prefixing the path - so the English pages rank as English pages.
Result
Six hours after launch, the first enquiry arrived.
It arrived through the AI System subpage, tagged by the hidden fields mapped to every call to action.
“The first inquiry came in six hours after launch, from a large company, and we knew exactly which page produced it. I had never had that before. The way he worked impressed me even more than the result.”
Ignacy Bochiński · Co-founder
The scope tells the rest. What began as one homepage became five pages, an English version, a blog with templates, HubSpot integration and technical SEO. Each time the brief widened, it widened because the last piece had landed.
Has your company outgrown its website?
Tell me what you’re building. I’ll tell you if I can help.