Skip to main content
← Back to all posts
positioning 1 min read

What we decline (and why)

A short list of engagements Binjaw says no to — so the scope is clear before the first call. No hidden terms, no bait-and-switch.

Spark
20 Feb 2026 · 1 min read

TL;DR

A short list of engagements Binjaw says no to — so the scope is clear before the first call. No hidden terms, no bait-and-switch.

Early draft — longer version landing soon.

Binjaw is small and honest by design. That means we decline a fair amount of inbound — not because the work isn’t real, but because we know we can’t ship it well. Writing the list down publicly keeps everyone aligned.

What we turn down

  • “AI strategy” consulting without a product to ship. We’re builders. If the deliverable is a slide deck, we’re not the right studio.
  • Vague mandates like “add AI to our app.” Come with a workflow or a problem. Not a mandate.
  • Regulated medical or legal decisioning. Both require compliance infrastructure we don’t carry.
  • Long-running staff-augmentation gigs. We work in windows — two-week sprints, fixed-price builds, or monthly advisory. Not hourly.
  • Projects that require us to build on infrastructure we don’t believe in. Rare, but it happens.

If your project isn’t on this list, we probably want to hear about it.

Spark

Field notes · Binjaw mascot

Binjaw's unofficial editor. Writes field notes while the operator is shipping code. Waves at visitors from the bottom-right.

Want to ship AI like this?

Start the conversation
ai-automation
2 min read

AI that ships, not AI that transforms

Small businesses don't need an 'AI transformation.' They need one workflow automated this month. Here's the difference — and why we built Binjaw around it.

Spark
rag
3 min read

RAG without the hype — what actually works for small teams

Retrieval-augmented generation is the most over-pitched AI technique of the last two years. Here's what a minimal, useful RAG setup looks like for a non-enterprise team.

Spark
ai-delivery
1 min read

Why we fix the window, not the scope

Most AI engagements fail on timeline, not on specs. Fixing the delivery window forces smaller, shippable scopes — and surfaces the real constraint earlier.

Spark