When the work doesn't fit a named shape.
Larger builds, multi-engagement programs, and vertical specialty work. Scoped together, fixed-price, written deliverables.
Most AI work in established businesses fits one of the named engagements. A Strategy Session for owners orienting to where AI belongs. An Investment Memo for a specific decision. A Pilot Recovery for a stalled project. A Workflow Automation Sprint for one defined workflow.
Some work doesn't.
You may be looking at three workflows that need to be automated as a coordinated program, not as separate sprints. You may have a multi-phase build where the Strategy Session is the first step, and the build is already scoped in your head. You may operate in a regulated industry where the engagement requires specialty work that the standard services don't cover. You may need both an Audit and an Investment Memo on the same timeline because the underlying decision requires both.
Hihnala Programs covers that ground.
A Hihnala Program is a custom-scoped engagement built from one or more named services, plus whatever specialty work is required. The structure stays the same: defined scope, fixed quote, written deliverables at named milestones, clean handoff at the end.
The difference is that the engagement is shaped around your situation rather than fitted into a standard shape. Sometimes that means combining two named services into one program. Sometimes it means a build that's larger than the Sprint accommodates. Sometimes it means vertical specialty work in a regulated industry where standard services need to be extended.
The constraint that holds across every Program: the engagement starts with a defined scope and ends with a defined deliverable. There are no open-ended retainers. No “let's see how it goes” engagements. No work without a written quote.
A few patterns where a Program fits and a named service doesn't.
A multi-workflow automation program.
You've identified three or four workflows that need automation, and they share data, systems, or operational logic. Building them as separate Sprints would duplicate scoping work and miss integration opportunities. A Program scopes them together and sequences the build to compound across workflows.
A combined assessment.
Your situation requires both an Audit (to map what's already running) and an Investment Memo (to decide what to do about a specific opportunity). The two engagements are related, their timelines overlap, and running them sequentially would waste effort. A Program runs them together with one scoping conversation and one final report.
Strategy plus build, scoped together.
Owners who are certain that a Strategy Session will conclude with a build sometimes prefer to scope both at once, with a defined break point in the middle. The Strategy Session outputs the build, and either party can step out at the gate without penalty.
Regulated-industry specialty work.
If your business operates under EU AI Act provisions, sector-specific compliance regimes, or industry-specific data governance requirements, the standard engagements may need to be extended. Programs accommodate the additional scope without forcing the work into a shape it wasn't built for.
Larger builds.
If the workflow you want automated touches more than four systems, requires custom development inside enterprise platforms, or depends on architectural changes beyond the Sprint's scope, the Sprint is the wrong shape. A Program covers builds at the next size up.
The category I'm most careful about declining is “ongoing partnership without defined scope.” Most owners who arrive looking for that don't actually want it. They want the calm of knowing someone is paying attention to AI in their business, plus the option to engage when something specific comes up. That's better served by completing one or two named engagements first, then deciding whether ongoing optimization is the right structure.
If you're looking for a fractional CTO, a permanent embedded consultant, or an AI lead on retainer, Hihnala isn't the right firm. The work I do is engagement-shaped by design.
If you're looking for a vendor relationship that quietly auto-renews and absorbs a defined budget without producing defined outputs, the same answer applies.
Every Program starts with a Discovery Call. Thirty minutes is rarely enough for Program-scale work, so we usually follow it with a longer working session, billed at a fixed scoping fee that's credited against the Program if you proceed.
The scoping output is a written proposal. It defines what's included, what's excluded, the deliverables at each milestone, the timeline, and the fixed price. Nothing starts until the proposal is signed.
The work runs in defined phases with deliverables at each phase boundary. You see progress weekly. You can step out at any phase boundary without penalty if the work isn't delivering what was scoped.
Starting at $15,000.
Hihnala Programs are fixed-price, scoped together before any work begins. The entry point sits above the top of the Sprint range so the boundary is unambiguous: anything below $15,000 fits one of the named services.
Every Program engagement starts with a Discovery Call. If your situation looks like Program-scale work, we'll schedule a follow-up scoping session and go from there.
When the right engagement is the one nobody else has named yet.
Book a Discovery Call. Thirty minutes. No pitch.
Book a Discovery Call →