How Engagements Work

Choose weekly development, a defined build or a reserved engineering engagement. We agree the scope, schedule, and commercial terms before work begins.


How Engagements Work

Different work needs a different structure

Weekly Dedicated Implementation moves one active workstream forward at an agreed subscription price, with engineering review, testing, and written progress updates. Fixed-price builds purchase agreed deliverables. One-on-One Engineering reserves Bill’s personal time exclusively during agreed engagement hours for implementation, pairing, meetings, or technical direction. Reserve recurring weekly capacity or a longer engagement. Compare the options.

Fixed-price builds cover a defined delivery phase

Custom builds start with paid discovery at an agreed fee. We define the scope, assumptions, and acceptance checks, then quote the build and schedule for your separate approval. The Working Prototype remains a defined 4–6 week package, with no additional discovery fee. Scope changes are agreed separately.

Review fixed-price builds and payment options.

Uncertain systems start with evidence

Existing codebases, rescue work, and open-ended technical problems are not forced into a false completion promise. They can begin with the Four-Hour App Rescue Assessment or move forward in approved consulting blocks as the real condition of the system becomes clear.

The accepted proposal is the boundary

A fixed price applies only to the delivery phase and deliverables in the accepted proposal. Added features, changed assumptions, and newly discovered work are reviewed in writing before they affect price or schedule.

Payment options are explicit

Your proposal specifies the prepaid total or an agreed installment plan before checkout. Installments fund a fixed project; they are separate from the Build Cycle service. Additional Build Cycles require approval, and dedicated time is scheduled before purchase.

Progress stays visible

Work is organized around reviewable milestones and practical evidence. When a decision, dependency, or change affects the agreed delivery phase, it is surfaced rather than hidden inside optimistic promises.

The honest expectation

Defined work receives a defined commercial structure. Uncertain work receives an evidence-first structure. Neither approach treats software as unlimited work, and neither hides uncertainty from the client.

The goal is a clear delivery boundary, an honest payment structure, and disciplined progress through the real system.