Engagements

Clear scope, fixed prices, no surprises

How a typical engagement runs from the first call to a monthly retainer, and the answers to the questions that usually come up.

The usual path

  1. Intro call 30 minutes, free

    Your stack, your on-call and what's hurting. You'll hear honestly whether automation would pay off.

  2. Readiness assessment about 2 weeks, fixed fee

    A ranked automation plan and a working prototype. Details

  3. Automation build fixed scope

    The runbooks, analyzers and guardrails from the plan, built in your environment. Details

  4. Retainer monthly

    Keeps the automation current as your systems change, and adds to it.

You can stop after any step. Database advisory clients usually start directly on a retainer.

Pricing models

OfferPriceModelWhat's fixed
Readiness assessment$7,500Fixed fee, paid at kickoffScope, dates and price, agreed up front. Credited toward a build started within 60 days
Ops automation buildFrom $36,000Fixed price per written scope; 50% at kickoff, 50% at handoverThe incident classes, deliverables and timeline in the week-1 scope
Automation retainer$2,500 or $5,000/moFlat monthly fee, billed in advanceHours per month and support response window
Database advisory$3,000 or $5,500/moFlat monthly fee, billed in advanceHours per month and escalation window

Builds larger than three incident classes are priced from about $10,000 per additional class. Every price is confirmed in writing before work starts.

Questions that come up

Who does the work?

Vitaliy Mogilevskiy, HASHJOIN's principal, does every engagement himself. There's no hand-off to junior staff.

What access do you need?

The assessment needs read-only access to incident history, runbooks and dashboards. A build needs access to a non-production environment and the same read-only production access your on-call engineers have. Credentials stay in your systems.

Who owns the code?

You do. Runbooks, parsers, tests and docs built for you are yours, delivered into your repositories.

Do we need a Claude subscription?

The runbooks run on Claude Code under your own account or API access, so your usage stays under your control and your data policies. The parsers run without any model.

Will you be on our on-call rotation?

Not by default. Retainers include support and escalation help within agreed hours and response windows, but your team stays the first responder.

Can you work through our vendor process?

Yes. HASHJOIN contracts business-to-business and works under a standard MSA and SOW. NDAs are fine before the first technical conversation.

Ready to talk?

Thirty minutes, no obligation.