A SaaS homepage where the product does the selling

What Ferrow is

Customer feedback arrives everywhere: an email to support, a message in Slack, a ticket in Zendesk, a note from a sales call, a post in the app. Ferrow collects all of it in one inbox, suggests which requests ask for the same thing, groups them into themes, links each theme to an issue in Linear or Jira, and emails everyone who asked once it ships.

The name comes from furrow, the groove a field is planted in, where small things grow in rows. That is the whole design idea: loose notes that line up into rows. It shows in the logo, six tiles in rows of three, two and one that also read as an F, and in the small coloured tiles that stand for single requests across the page.

The problem the page had to solve

• Sell without proof it does not have. No customer logos, no testimonials, no user counts, no “save 10 hours a week”, no security badges. The product has to make the case by itself.
• Show a workflow, not a feature list. Ferrow is useful because of what happens between a note arriving and a customer hearing back. The page has to walk through that in order.
• Stay readable while showing a lot of product. Inboxes, themes, roadmaps and reports are dense. Every panel needed real, readable content without turning the page into a wall of interface.
• Look premium without the usual SaaS tricks. No glowing gradients, no 3D blobs, no four equal stat cards. Flat colour, real type and product panels that work.

A hero that files its own feedback

The first screen is near-black green with the headline “Every customer request, sorted into what to build next.” Inside the headline sits a row of three small tiles, three notes lined up, so the brand idea is in the type itself. Two loose notes, a sales call and a Zendesk ticket, sit beside the buttons at a slight angle. As you scroll, they drop straight down and slide in behind the product window, as if filed.

The window below is the product. It starts tilted back and flattens as you scroll into it. On the left, an Incoming list of requests, each with its channel as a small pastel chip. On the right, a table of themes with request counts, a “+ today” number and a strip of tiles coloured by where each request came from. Every few seconds a new request arrives, is matched to a theme and files itself into that row, and the count goes up. It is the one thing on the page that moves on its own.

Seven channels in, the work out

Instead of a row of logos, the integrations are drawn as a flow. Gmail, Slack, Intercom, Zendesk, HubSpot, Zoom and the Ferrow widget sit on the left, each tagged with its channel. Thin curved lines run into a dark Ferrow card in the middle, and out again to Linear, Jira, a Slack digest and the customers who asked.

When the section comes into view, one note in each channel’s colour travels along its line into the hub and lands as a tile in a theme row, and the counts tick up. Then one note goes out to each tool. Hover any channel and it sends another.

Four steps, pinned while you scroll

“From a note in someone’s inbox to a line in the changelog” is told in four steps: Collect, Sort, Plan and Close the loop. On a wide screen the step list and the product panel stay pinned together while you scroll. All four steps stay in view, the active one opens its text, and a thin bar along its top fills as you scroll through it. You can also click a step to jump to it.

The panel sits on a pastel stage that changes colour with each step, and each panel plays a small entrance when its step opens: inbox rows rise in, a suggested duplicate slides in with a Merge button, a roadmap bar grows across the timeline, and the “shipped” email assembles line by line. The channel filters in the inbox work.

A roadmap that ships while you watch

The roadmap sits in its own product window: Under review, Planned and Shipped, each card with its status, its ID, a row of request tiles, the linked issue with a small progress bar, and the faces of the people who asked. When the board comes into view, the Bulk export card moves from Planned to Shipped, its tag turns mint, the column counts change, and a dark note drops into the window’s top bar: “Bulk export shipped. 128 people will hear about it.”

A switch in the corner turns the team view into what customers see. The header becomes Northwind’s public roadmap with a Suggest an idea button, and the private notes on every card give way to working vote buttons.

Reports, not a row of stat cards

Four equal coloured cards with big numbers are the most common SaaS section there is. Ferrow’s reports are a dashboard instead. The main card shows 1,284 requests with a chart built from the same note tiles as the rest of the page, one column a day, coloured by channel. Hover a column and it shows its date and count. Beside it, a split bar and list by channel, then a ranked list of top themes, and three small pastel cards for open themes, roadmap items and people waiting to hear back.

The 7 days, 30 days and Quarter buttons redraw all of it: seven daily columns, thirty days or thirteen weeks, with every number scaled to match.

Ask inside the app, hear back inside the app

The changelog is drawn as Northwind’s own changelog page: a timeline with the newest entry open, export to CSV with the columns it includes, and two earlier entries below it. Those are the same features that sit under Shipped on the roadmap, so the page tells one story from request to release.

Beside it, the in-app widget sits on a page of Northwind’s app. When it comes into view it plays through once on its own: it opens, types a request and sends it, then shows similar requests to vote on. Tabs above it show every state: closed, open, typing, an error for an empty message, and sent. The form works too.

Pricing you can try on

Pricing is per workspace, and customers who post, vote or read the roadmap never count as seats. Above the three plans, a slider asks how many teammates sort and plan. Move it and the plan that fits is marked “Fits your team” and its monthly price is worked out, extra teammates included. The yearly switch, with its “2 months free” chip, recalculates everything. Each plan has its own tile mark, one, three, or three and three, and a full comparison table opens under the cards.

The brand system

The palette comes from Mahadeva, a Framer template by Breeje Anadkat, measured from its live page: near-black green #0E1E1D, white, a warm cream for pricing and questions, and flat pastels in mint, sky, lilac, butter, peach and pink. In Ferrow the pastels carry meaning. Each one stands for a channel: sky for email, lilac for chat, butter for support, peach for sales calls and mint for the widget. Mint also means shipped.

Display type is Almarai, with Geist for numbers, product panels and card titles, and Geist Mono for small labels and IDs. Corners are 4 pixels everywhere and 2 pixels on tags. There are no shadows or gradients: panels separate by colour. Buttons carry their arrow in a square box on the right.

The logo came from three options: a lowercase f with a crossbar of tiles, two tiles in a row with a third tipping in, and the one chosen, six tiles in rows of three, two and one. It holds up at 16 pixels in a browser tab and at full width in the footer.

Sound on

Motion with a job

• One opening. On load the headline rises line by line, its tiles pop in, and the window rises while its counts tick up.
• One loop. New requests arriving in the hero window is the only thing that repeats, and it pauses when the window leaves the screen.
• Moments that explain the product. Notes file into the window, travel into the hub, a card ships, the widget sends a request and a first import fills its themes. Each plays once, when its section appears.
• Calm by request. For visitors who ask their system for reduced motion, nothing plays on its own and the four steps sit in a still grid. The page is complete without motion.

Fast and easy to read

• Light to load. On a phone profile the page loads in 5 requests and about 140 KB, with the largest element on screen in about 2.2 seconds. The typefaces and animation code are served from the site itself, and every product panel is HTML and CSS, so there are no screenshots to download.
• Steady while scrolling. Nothing on the page jumps while it loads or scrolls.
• Easy to read. Every line of text passes the WCAG AA contrast standard at desktop and phone sizes, including inactive steps and the small labels in the product panels.

Built for phones

On a phone the window shows two incoming requests and three themes, the integrations stack as channels, hub and tools, the four steps sit open one under another with their panels, and the roadmap, dashboard and pricing cards stack in a single column. The menu opens from the top with every section and the main button.

Ready for Framer

Ferrow was planned for Framer from the first section. Each section maps to one Framer component, and every state on the page, the widget’s five states, the team and public roadmap, the date ranges, monthly and yearly pricing, becomes a variant of that component. Colours, type, corners and spacing sit in a small set of shared styles, and the scroll moments map to Framer’s own scroll and appear effects.