Hire an embedded product design team

Less than most teams expect, but three things are not optional. Access to the product and to your analytics, including session recordings if you have them. One person who can answer a question without a meeting being scheduled. And a shared view of the two or three things that matter most this quarter, even if that view is rough.

Beyond that we ask for two to four hours of stakeholder time in the first week, usually as a workshop with whoever owns the product, and an introduction to your dev team so the designer understands what is cheap and what is expensive to build. We do not need documentation written for us. If your context lives in Slack threads and half-finished Figma files, that is normal and we will read it.

Four weeks is the shortest engagement Other Land takes. That covers one scoped piece of work and gives both sides a read on whether the model works, though onboarding takes a real share of it, so most teams book longer. After the first four weeks it continues month to month for as long as it is useful, with no fixed end date and no renewal negotiation.

To stop, tell us two weeks in advance. There is no exit fee, no minimum remaining term, and no penalty for stopping earlier than you planned. The designer finishes what is in flight, hands over files and specifications in your format, and writes down the open decisions so nothing has to be reconstructed later. Our longest partnership on this model ran four years, one month at a time.

We replace them within a week and re-onboard the new designer at our own cost, not yours. This is the risk you carry with any hire, and it is the one part of hiring that Other Land can genuinely take off your side of the table.

It rarely gets that far, because the design lead and the PM are in the work from the first week, so a mismatch of level, domain or communication style usually surfaces internally before it becomes your problem. If it does reach you, say it early rather than politely. A fit problem named in week two costs a week. The same problem raised in month four has already cost you a quarter of roadmap.

A design lead and a product manager, included in the fee rather than billed on top. The design lead reviews the work weekly, sets the quality bar, and is the person who says the uncomfortable thing when a direction is not working. The product manager keeps the engagement aligned with your priorities, handles scope conversations, and makes sure the designer is not quietly blocked.

In hours that is roughly two to four hours a week each, and it scales up when a decision is large or a deadline is close. This is the actual difference between an embedded team and staffing a seat. A single freelancer, and often a single in-house designer, has no design leadership checking the work at all.

Per month, usually yes. Over the first year, usually no, and the honest answer depends on your market. There is no recruitment fee, no equity, no severance, no hardware, no benefits, and no two to four months of salary paid while someone ramps up or while the role sits empty. A senior hire who does not work out is the expensive outcome, and that risk sits with us.

In-house wins clearly if you can hire a strong senior product designer locally, keep them fully busy, and keep them for several years. Then in-house is cheaper and the accumulated context is worth more than anything Other Land can offer. If any part of that sentence is uncertain, the embedded model is the cheaper bet.