Work we decline, and why that helps you

Selectivity is a delivery practice

We keep a small active portfolio so the people who scoped the work are the people who review it. That only works if we decline work that would force a different company to exist: a bench of interchangeable engineers, a design studio, or a round-the-clock operations center.

Saying no early is not branding. It is how we protect the commitments we make to the clients we do take — independent review, a written plan, and a handoff someone else can use.

Three shapes we are not

If you need one of these, you should hire someone who is built for it. We will say so, and where we can, introduce a better-matched partner.

• Staff augmentation. We do not rent out engineers to join your stand-up indefinitely. If you need a team under your management, that is a different market and a different contract.
• Design-only web production. We will not take a project whose entire outcome is a marketing surface with no workflow, data, or operating path underneath.
• 24/7 managed operations. We are not an on-call center. Ongoing support exists only when we agree it, with boundaries, and never as leftover access after a build.

What we take instead

We take work with a concrete business outcome that touches live users, operations, data, or existing systems. The first conversations map that outcome, the constraints, and whether a project or an advisory engagement is the right shape.

Typical projects are scoped, quoted, and time-bounded. They live in a range you can plan around — most often one to eight months, and commercially in the $5,000 to $40,000 band — because the problems we are good at have edges. If the work is larger than that, we say so and propose a first slice that can be finished.

A first slice that can be handed off is more honest than a transformation that cannot be scheduled.

How to use a no

If we decline, you should leave with more than a polite refusal. You should leave with a clearer name for the help you need. “You need a product designer and a content lead, not a systems team.” “You need an embedded engineer you manage.” “You need a managed vendor for this SaaS, not a custom integration.”

That sentence is often worth the conversation. It is also why the first calls are complimentary. We would rather spend an hour telling you the truth than spend a quarter doing work that was never ours.

Ask this of anyone you hire

Ask what they will not take, and what happens when they are wrong about fit. A partner who can only describe their yes is selling capacity. A partner who can describe their no is selling judgment.

If your problem is a product or system that has to keep working after launch, and you want a written plan, independent review, and a handoff your team can use — that is the work we take. If it is not, we will tell you quickly.