The team

Four people. You will talk to all of them.

No account managers, no handover between a sales team and a delivery team. Whoever answers is whoever builds it.

Flux_Dev_A_professional_corporate_headshot_of_a_confident_busi_1

Design

Sara Burns

Design lead

Owns the token layer. Writes about why colour pickers should never show a hex field.

Flux_Dev_Professional_studio_portrait_of_a_middleaged_man_with_2 (1)

Engineering

Marcus Keel

HubSpot developer

Field architecture and module refactors. Knows every upload error HubSpot does not document.

Lucid_Origin_Blackandwhite_portrait_of_a_senior_executive_male_1

Content

Jen Park

Content strategy

Writes the help text. Argues that a good field label saves a forty page handover doc.

Lucid_Origin_Blackandwhite_portrait_of_a_senior_executive_male_2

Studio

Tomas Mielke

Founder

Started the studio after inheriting one broken site too many. Still takes client calls.

42

Modules

34

Templates

7 /7

System pages

0 kb

jQuery loaded

How four people work

Small enough that nothing needs a process.

These are not values on a wall. They are the three habits that make a team this size possible.

01
Written before spoken

Two calls a week, everything else in writing. It means you can read why any decision was made, years later, without asking anyone.

02
Everyone ships

No one here only reviews. The person who designs a module also writes its help text and answers the support question about it.

03
Say no early

Turning down work we would do badly is the reason the four of us can stay four. We say it on the first call, not in week three.

They told us on the first call that half of what we asked for was a waste of money. We hired them that afternoon.

Daniel Okonkwo

Operations Director, Calder Manufacturing

We are hiring a fifth.

Four open roles, all funded, all remote across EU time zones. The longest take-home is three hours and we pay for it.

See open roles