Your product outgrew its website.

An independent design-engineering studio for B2B SaaS, AI and developer tools.

proofline · Studio concept

Direction: Tick & Tie

Measured: 100 / 100 / 100 / 100Lighthouse, all 5 pages443–563 msLCP, min–max0CLS, max

2026-10-09 · lab run, not field data · Lighthouse 13.4.1, desktop preset · scores: performance / accessibility / best practices / SEO Full conditions

Signature: A stack of typeset documents and a red pencil trace from the forecast total to the bank-statement line.

Read the breakdown Open the live site

First screen of the Proofline site at 1440 × 900: on dark green baize, a stack of three typeset documents — a 13-week cash forecast, a ledger and a bank statement — joined by a red pencil line from the forecast total to the statement line, with the headline “Cash forecasts you can sign off on.” on the left.

First screen of the Proofline site on a phone, 390 × 844: the headline above a compact stack of the same three documents, with the red trace and its check marks.

Three products, three directions.

Proofline, above, is one of three. All three are studio concepts — fictional products with no client behind them — and all three are live.

First screen of the FlakeKill site at 1440 × 900: on a near-black background, the headline “Your CI is lying to you.” over a field of green and red test-run cells, and a card for one test, auth.spec.ts › login, whose runs flip between pass and fail on the same commit.

First screen of the FlakeKill site on a phone, 390 × 844: the headline over a band of run cells, with the test card below the buttons.

flakekill · Studio concept

Direction: The Pulse

Signature: A live strip of test runs, and the quarantine that pulls the lying test out of the grid.

Read the breakdown Open the live site Compare the measurements

First screen of the tracelayer site at 1440 × 900: on a near-black background, the headline “See every step your LLM app takes.” on the left and, on the right, the spans of one request laid out in depth along a time scale.

First screen of the tracelayer site on a phone, 390 × 844: the headline and buttons above the field of trace spans.

tracelayer · Studio concept

Direction: Deep Trace

Signature: A live, clickable call tree of an LLM request, with a piece of it opening every inner page.

Read the breakdown Open the live site Compare the measurements

Three sites, one set of measurements.

In place of client logos, which the studio doesn't have yet: measurements you can repeat.

Measurements of the three case-study sites, 2026-10-09
	proofline	flakekill	tracelayer
Pages measured	5	3	6
Lighthouse — performance / accessibility / best practices / SEO, every page	All three100 / 100 / 100 / 100
LCP, min–max	443–563 ms	526–604 ms	524–645 ms
CLS, max	All three0
TBT, max	All three0 ms
Site weight (JS · CSS · fonts)	289.5 KB (21.4 · 72.6 · 62.7)	411.2 KB (44.0 · 99.6 · 88.1)	379.9 KB (44.4 · 62.6 · 169.0)
axe violations	All three0
Console errors	All three0
Without JavaScript: hidden content / dead forms	All three0 / 0
Overflow sweep: points checked / overflows found	680 / 0	408 / 0	816 / 0

Measured 2026-10-09 on each site's current build, every page, same tool versions: Lighthouse 13.4.1, desktop preset; axe-core 4.12.1; Chromium (playwright-core 1.62.1); local static server; Ubuntu 24.04 in WSL2. A lab measurement of the build, not field data from visitors. Overflow sweep: 360–1440 px in 8 px steps, every page.

Check it yourself: open a live site in PageSpeed Insights and choose Desktop. Expect different values — a public test adds the host's server and network, which this lab run didn't have.

Pages measured: proofline5flakekill3tracelayer6
Lighthouse — performance / accessibility / best practices / SEO, every page: All three100 / 100 / 100 / 100
LCP, min–max: proofline443–563 msflakekill526–604 mstracelayer524–645 ms
CLS, max: All three0
TBT, max: All three0 ms
Site weight (JS · CSS · fonts): proofline289.5 KB (21.4 · 72.6 · 62.7)flakekill411.2 KB (44.0 · 99.6 · 88.1)tracelayer379.9 KB (44.4 · 62.6 · 169.0)
axe violations: All three0
Console errors: All three0
Without JavaScript: hidden content / dead forms: All three0 / 0
Overflow sweep: points checked / overflows found: proofline680 / 0flakekill408 / 0tracelayer816 / 0

Measured 2026-10-09 on each site's current build, every page, same tool versions: Lighthouse 13.4.1, desktop preset; axe-core 4.12.1; Chromium (playwright-core 1.62.1); local static server; Ubuntu 24.04 in WSL2. A lab measurement of the build, not field data from visitors. Overflow sweep: 360–1440 px in 8 px steps, every page.

Check it yourself: open a live site in PageSpeed Insights and choose Desktop. Expect different values — a public test adds the host's server and network, which this lab run didn't have.

Two services. Published prices.

Direction Sprint

Test the studio on your own product before committing to a full site.

$1,000price
5 working dayslength

Included

A review of your product, your audience and your current site
The product story and the structure of your home page
Two distinct art directions
One high-fidelity, interactive prototype of the first screen
A recommended direction and a plan for the next steps

Not included

Design of every page
Code beyond the prototype
Final copy for every page

Revisions: one round.

Continue to a Custom Website within 60 days of delivery and the $1,000 counts toward its price.

100% up front · USD · by invoice

Write about a Sprint What to send for a Sprint

Custom Website

from $4,500price

Included

Page structure and UX
Copy for the pages in scope
Original art direction and visual design
Responsive layout and code
Interaction, to the agreed extent
Quality checks
Help with launch

Priced separately

Additional pages
Complex interaction
Integrations
Ongoing support

Larger projects get their own proposal.

Usually 2–3 weeks — most of it is your review time.

50/50 · USD · by invoice

After the final payment, the code and design are yours and the repository is handed over.

Prices are indicative until the scope is agreed. The written proposal fixes the price, pages, timeline and revision rounds before work begins.

Write about a website

From the first email to launch.

Email — a reply within one working day.
Written proposal — read it, question it, agree to it.
Direction — as a Sprint, 5 working days.
Build — usually 2–3 weeks, mostly your review time.
Measurement — speed, accessibility, the site without JavaScript.
Launch on your host, then the handover.

See how a project runs

Start with one email.

hello@firstfold.studio

Write to the studio

The button opens a new email in your mail app, with the subject and these prompts filled in. If nothing opens, copy the address and write from any inbox.

What to include

Your product, in a sentence or two
A link to your current site
When you need the new site
Your budget — a range is fine

1 working day
to reply to your email
In writing
scope, price and timeline, before work begins
One or two
projects at a time