Achieve scale and profitability with design-led engineering.

Clear product decisions connect business goals to work people can use. We design interfaces, build prototypes, and ship production front-end code with founders.

Start a conversation

Getting it built is only the start.

A working feature still needs a clear purpose. The interface has to show people what they can do and why it matters.

  • Choose the job

    Start with the person, task, and reason the product matters to the business. We decide what the first version needs to explain and what can wait before building.

  • Cut to focus

    A feature needs a reason to stay. We make that choice explicit, then carry it into screens and their states so the team can review the decision in context, including edge cases.

  • Beyond the demo

    The first version covers more than its main path. Empty states, failed requests, and slow connections shape how a product works; design and implementation account for them.

  • Two readers

    Every control needs a name an agent can read. Agents are software acting for a person: AI assistants, browser and coding agents, and tools they call while carrying out a task.

  • Decide in the code

    We test product decisions in working prototypes and production front-end code. The running interface gives the team a concrete place to review what needs to change.

  • Yours to keep

    Code and decisions live in your accounts from day one. Paid work becomes yours after payment; we keep our tools and general know-how. Third-party terms still apply.

Selected work

Plate XVIII. Soft light.

Drivepoint

Drivepoint makes strategic-finance software for consumer brands. Design and prototyping covered core customer-facing features across the web application and product touchpoints.

Role
Product design engineer
Years
2023–2026
Platform
Web, Excel
Scope
  • Interface design
  • Design systems
  • Front-end development
Plate II. Dapple.

Pantastic

Pantastic made commerce tools for independent brands. Work covered shopper and merchant design directions, campaigns, and prototypes deployed with product and engineering.

Role
Founding product designer
Years
2020–2023
Platform
Web
Scope
  • Product direction
  • Prototyping
  • Front-end development
  • Marketing design
Plate III. Glare.

Photo Butler

Photo Butler let people share event photo streams with AI-curated photos. Work covered product direction, interface design, business-model concepts, and brand-partnership concepts.

Role
Founding product designer
Years
2015–2019
Platform
iOS, web
Scope
  • Product direction
  • Interface design
Plate IV. Current.

Nanigans

Nanigans was moving from managed campaigns to advertiser-run software. Work covered Ad Engine onboarding and a customer success site with product, marketing, and support.

Role
Product designer
Years
2013–2015
Platform
Web
Scope
  • Interface design
  • Website design
  • Front-end development
Plate V. Rain.

Lumatic

Lumatic City Maps showed walking and transit directions as route photographs. Work covered the existing iOS redesign, Android app guidelines, and marketing and developer websites.

Role
Founding product designer
Years
2012–2013
Platform
iOS, Android, web
Scope
  • Interface design
  • Website design
Plate VI. Tide.

Proudcloud

Proudcloud builds web and mobile software for startups and larger companies. Product design covered customer projects, with front-end work alongside founders and engineers.

Role
Lead product designer
Years
2010–2012
Platform
Web
Scope
  • Interface design
  • Front-end development
Plate VII. Field.

GoAbroad.com

GoAbroad lists study, volunteer, teaching, and internship programs abroad. Work covered a customer dashboard, sales and finance tools, and prototypes with staff and engineering.

Role
Product designer
Years
2008–2010
Platform
Web
Scope
  • Interface design
  • Prototyping
  • Website design
  • Usability testing

About

Kwirita is a design strategy and engineering studio for pre-seed and seed founders. We turn early product questions into decisions, interfaces, and working software.

How a month runs

The work runs one month at a time. Founders keep the priorities; the monthly task list sets what moves forward.

A written plan is ready in the first week. Working software is available every week, starting in week one. A written note goes out every Friday, Manila time, covering what shipped, what changed, and the decisions that need attention. A weekly 30-minute call is for decisions and is skipped when there is nothing to decide.

Product direction

Decide what the first version does, who it serves, and what can wait. We turn those choices into a written plan that the team can review against its current priorities.

Interface design

Flows, screens, their words, and their states, including empty and error cases. A shared design gives the team a place to review the task, decisions, and next steps.

Front-end engineering

The interface, built in your own codebase and reviewed like any other code. We build it with the least access needed, keeping design decisions close to the working implementation.

Agent readiness

Generated page text and Markdown let software tools inspect public pages. Each copy reflects the page at build time; later weather and interaction changes are not included.

A system that lasts

Tokens and components, with notes on why each choice was made. Code and notes stay in your accounts from day one, giving the team a reference for future design decisions.

Working prototypes

A front-end prototype you can click through, deployed so your team can try it on real screens. We code it ourselves, so the small details get settled in the code itself.

Pricing and terms

Prices in USD. Monthly terms. Cancel anytime.

One task at a time

One task stays in progress at a time, chosen from a list you keep in order. Each task is one piece of work you can review on its own, ending in something usable.

$6,000

per month

Two tasks at a time

Two tasks can be in progress at once, for a team working on two fronts. Both come from the same founder-ordered list, so priorities stay visible when work moves between tasks.

$10,000

per month

Other ways to start

A working session

One hour of product advice, paid in advance. If you subscribe within 30 days, we credit the full price to your first month. This stays separate from monthly work.

$300

per hour

A first-version review

Written interface and front-end review with agent readiness arrives within a week, with a walkthrough call. If you subscribe within 30 days, we apply its full price to month one.

$2,500

per review

Terms

One month at a time, paid at the start of each month. Cancel any time. Work continues to the end of the month paid for, and nothing renews after it. Read the terms.

A task is one piece of work you can review on its own, ending in something usable: a designed flow, a merged pull request, or a deployed prototype. Larger requests are split into tasks and described up front.

Tell us what you’re building.

Bring the product question that needs attention. A few lines are enough: what it does, who it’s for, and what needs to change. We reply within two working days, Manila time.

Start a conversation