Services built to ship.

Design, engineering, and strategy across eight services, each shaped by the kind of work B2B companies, enterprise brands, and agencies actually bring us.

Trusted by teams at
1PasswordiHeartMediaPernod RicardDripsFlareLandingChattr

Three ways to work with us.

Most engagements fall into one of these shapes. We'll recommend the right fit on our intro call.

01

Fixed-scope project

For teams with a defined deliverable and timeline. Marketing site, product launch page, e-commerce build. Scoped up front, shipped against the deadline you bring us.

Best forOne-time builds with clear goals
02

Embedded team

For teams that need senior design and dev capacity but aren't ready to hire. We plug into your sprints, standups, and tools as an extension of your team.

Best forTeams with ongoing work
03

Ongoing retainer

For companies whose website is a living asset. Monthly support for iteration, optimization, and new launches, without re-scoping every time.

Best forSites that keep evolving

In their own words.

Alkali did a great job assisting us with our project. Their specific domain knowledge was instrumental. They communicated effectively, collaborated with us on requirements, and delivered on time.
Anna Pobletts
Head of Passwordless · 1Password
Read the 1Password Case Study
1Password
HelloGina
Adept AI
BuildASign
Do you work in our existing codebase, or do you start fresh?
Both. Most of our engagements are additions to or rebuilds of existing applications. We're comfortable in unfamiliar codebases and will spend the first week getting oriented before we ship.
What if our stack is something you haven't used before?
It rarely ends up being an issue. We've picked up unfamiliar stacks at project kickoff plenty of times, and worked through no end of third-party integrations, some with excellent API documentation and some with almost none. Senior engineers read unfamiliar code quickly, so as long as the codebase is reasonably maintained, we're productive within the first week.
Do you do design and development, or just one?
Both. That's the point. The designers and engineers work together on every project, so there's no handoff gap between a Figma or design file and what actually ships.
Who owns the code?
You do, 100%. It lives in your repo (or gets transferred to your repo at the end of the engagement). No lock-in, no licensed framework you're stuck with, no retainers required to keep the lights on.
What happens after launch?
Most clients move to a monthly retainer for ongoing iteration. If you'd rather take it in-house, we document everything and do a clean handoff. Your team can be running the app locally within a day.
How long does a typical web app project take?
It depends on scope and complexity. Focused builds or feature additions come in faster, larger custom applications run longer. We give you a specific timeline once we've scoped the work on our intro call.

Let’s build something together.

A 30-minute call. We’ll listen, dig into the details, and tell you honestly whether we’re the right partner, or point you to someone who is.

Book Intro Call