Skip to content

Services

Design, engineering and launch, from one bench.

Hire us for one, or all three. Either way you get one small team, one plan and one Friday demo, not three vendors pointing at each other.

git push✓ 42 testsdeployed 01 design02 engineering03 launch

Service 01

Product design

We find out what your users need badly enough to switch, then design the smallest product that does it well. Sketches first, then prototypes tested every week with real people, then a design system your next hire can pick up on day one.

Typical length
4 to 8 weeks
Typical team
2 designers, a partner

What you get

  • ✓Five to fifteen user interviews, with notes and the quotes that changed our minds.
  • ✓Tested prototypes of your core flows, on the devices your users carry.
  • ✓A design system in Figma with tokens matching the code.
  • ✓A release map with a cut line: what ships first, what waits.

Good fit if you have a strong hunch and a fundraising clock, but no designer yet.

Service 02

Engineering

Web apps, iOS and Android apps, APIs and the integrations that make them useful: payments, messaging, sensors, partner data. Deployed from the first week, demoed every Friday, built with boring, well-known tools your own engineers will be glad to inherit.

Typical length
8 to 16 weeks
Typical team
2 to 3 engineers, a designer

What you get

  • ✓Production code in your repository from day one, reviewed and tested.
  • ✓Hosting, monitoring and alerts set up in your accounts, not ours.
  • ✓Architecture notes and a recorded walkthrough of every part.
  • ✓Help hiring your first engineers: the job post, interviews and onboarding.

Usually: TypeScript, React, React Native, Node, Postgres. We will use what you have if it works.

Service 03

Launch

A launch is a plan, not a post. We work out who should hear about it first, write the words, build the launch page and onboarding, and sit with you through launch week and the first 30 days of numbers.

Typical length
3 to 6 weeks
Typical team
A strategist, a designer

What you get

  • ✓Positioning in one page, tested on ten target customers.
  • ✓A launch site and app store pages, with the analytics wired up.
  • ✓Onboarding emails and in-app guides for the first two weeks.
  • ✓A 30-day dashboard and a review meeting at the end of it.

Engagement models

Three ways to work together.

Most common

Fixed sprint

A fixed scope, team and price for 6 to 16 weeks. Best when the problem is clear and the deadline is real.

  • · Price agreed up front, paid in three parts
  • · Scope changes swap work, never add cost
  • · 30 days of support after handoff

Flexible

Monthly retainer

A steady team, billed every four weeks, for three months or more. Best when you are still learning what to build.

  • · 10% below the sprint rate
  • · Change direction every Friday
  • · 30 days’ notice to stop

For teams

Build to hire

We build the first version and hire your first two or three people while we do, then hand the product to them.

  • · Sprint pricing, plus hiring support
  • · Your hires pair with us for four weeks
  • · No placement fees

Not sure which fits? Answer three questions.

Is the first release clearly scoped?
Do you already have engineers on staff?
Do you want your own product team within a year?

Our suggestion

Answer all three

We will point you at the model most founders in your spot pick.

Open the estimator

Questions

What founders ask on the first call.

and one we wish they asked: “what won’t you build?”

Do you take equity instead of cash?

Not as a replacement. For seed-stage clients we can take up to 15% of a sprint fee as a SAFE on the same terms as your round. Most founders do not ask.

Who owns the code and designs?

You do, from the first commit. Everything lives in your accounts: repository, hosting, Figma, analytics and app stores.

Do we have to come to Little Rock?

No. Most clients are elsewhere in the US. We ask for a two-day kickoff in person, at our studio or at yours; after that it is Slack, calls and the Friday demo.

How much of our time will it take?

Two to six hours a week from a founder who can make product decisions, more in the first and last weeks. The process page shows it week by week.

What won’t you build?

Crypto tokens, ad-tech, anything built to keep people scrolling, and products whose main job is collecting data about people who never signed up.