Small studio · Web & product

Manyana
Dev

I build the thing people can open, not the deck that describes it. Public work is named below; client work that can't be named stays that way.

jack@manyana.io

Studio

Just me.
Still.

Manyana Dev started in 2022 as a one-person studio. That hasn't changed. On small teams I usually own frontend, testing, and a large share of delivery; if the work also needs backend, integrations, or DevOps, I take that rather than invent a department.

“Best hire I've made for a build. He was calm about the messy bits and still shipped on the date we named.”

Fiona M

Approach

Put it in writing.
Then build.

I don't start from a process deck. Send the product, the hard constraint, and the date you need it; I send back a short page that locks surface, stack, and what done means. That page is what I build against until you have the repo.

If we got the brief wrong, we rewrite it before the codebase swells. I don't sell retainers.

The note

An email with product, constraint, and date is enough. I come back with what I need to price it.

The page

We agree scope and done in writing. That becomes the only brief.

The file

You get working software, the repo, and enough to keep it. Next email is only when there's more to do.

Contact

Start with an
email.

Product, constraint, date. That's enough. The form below writes the same mail if you'd rather not open your client.

jack@manyana.io

Prefer mail? jack@manyana.io · Read the CV →