Most agency processes are built around meetings. Weekly status calls, daily standups, alignment sessions, feedback reviews. For the agency, this creates visibility. For the founder, it creates calendar overhead.
We work differently. Here's what async-first means in practice — and what you actually get from it.
A daily standup requires everyone to be in the same time zone at the same moment, interrupt their flow state to report status, and process information in real-time that could be communicated better in writing.
We have clients in Paris, Berlin, New York, and San Francisco. A daily standup that works for all of them doesn't exist without someone suffering.
More practically: the information in a standup is better stored as text. "Built the hero component, blocked on brand colour confirmation" is more useful as a Linear comment with a screenshot than as a sentence spoken and forgotten. The async record serves both parties — you can check status without messaging us, and we can check your feedback without a scheduled call.
We commit every working day. This means you have a live view of progress without asking for it.
A typical daily commit includes:
If you want to look at the deployed preview, the link is always live. If you want to review the code, the repository is always accessible. You never need to ask "where are we?" — the answer is always current and available.
We include two rounds of design revision in every project. This is not a limit designed to protect us from work — it's a structure that produces better outcomes.
Round one is the first complete design presentation. Not wireframes, not concepts — a fully designed set of pages. We present it with written explanation of every major decision: why we made the colour choice, why the hierarchy is structured this way, what the mobile version does differently. You review it with context, not just screenshots.
Round two is the revision round. You give consolidated, written feedback. We implement it. The design is approved.
The constraint forces consolidation. "The hero feels too heavy" is a round-two note. "The hero feels too heavy, the CTA is too small, and I'm not sure about the font" is also a round-two note — addressed together, not as a stream of individual messages over two weeks.
Without a revision cap, projects run indefinitely through micro-adjustments that never satisfy because they're never consolidated. The cap protects you as much as it protects us.
Figma for design. Shared with you from day one — you can watch designs appear in real time if you want to, or review them when they're ready.
Linear for project management. Every task is a Linear issue with status, assignee, and notes. You have observer access and can see every open task and its current state.
GitHub for code. Private repository, you have full access from project start. We work in branches, open PRs for review before merging, and tag every release.
Vercel for deployment. Every branch gets a preview URL. The production URL goes live on the day we agree. No "deployments pending your infrastructure team" — it's live when we say it's live.
Loom for design walkthroughs. When we present a design round, we record a short Loom walking through the decisions. You can watch it at your convenience, pause it, and write feedback directly below it. This beats a synchronous design call for most clients.
Async-first doesn't mean async-only. There are moments where a call is better than text:
Discovery. The first 45-minute call is the most important thing we do together. We need to hear you describe the brief in your words. No questionnaire captures this fully.
Design round one. Some clients prefer to walk through the first design together. We accommodate this — the Loom is the default, but a 30-minute walkthrough call is available if preferred.
Decisions that would take 20 emails. When a complex decision needs rapid iteration — technical architecture, major scope changes, thorny copy questions — a 20-minute call beats a 48-hour async thread. We'll suggest a call when this applies.
Outside these moments, we default to written communication. Linear comments for project tasks. Email for billing and contracts. Slack (if you prefer it) for quick questions.
Every project includes 30 days of post-launch support. This covers:
It doesn't cover: new pages, new features, design changes, or CMS training beyond the initial session. These go into a change order.
After 30 days, ongoing support is available as a monthly retainer or on an ad-hoc basis — contact us for details. Most clients with simple, stable sites don't need either.
The async structure isn't about us working fewer hours. It's about eliminating the communication overhead that accounts for 30–40% of most agency engagements without producing anything.
When we're not in meetings, we're building. When you're not in meetings, you're running your company. The deliverables are what matter — the site, the code, the design files. The process exists to produce those, not the other way around.
Founders who work best with us tend to prefer written communication, can consolidate feedback rather than sending it in streams, and trust the process enough not to need daily reassurance. We earn that trust with daily commits and always-live previews.
If you need a high-touch, always-on agency relationship, we're probably not the right fit. If you need excellent work with minimal friction, we are.
Want to see what our process looks like on a real project? Start a conversation — we'll walk you through how we'd approach your brief specifically.
We take on a small number of projects each quarter. Tell us what you're building.
How to get a website made, step by step, with zero technical background. Pick the right type, compare your real options, prepare properly, and own everything.
A discovery call isn't a sales call. It's the step that determines whether a project succeeds or fails before a line of code is written. Here's what it covers and why skipping it is expensive.