How we work · fixed scope
Three sections · same principal on every engagement

Fixed scope. Four-step rhythm. Versioned artifacts.

Every Boldbard engagement runs on the same operating model — a fixed scope pinned before the first artifact is written, a four-step rhythm from discovery to handoff, and a discipline that keeps every SuiteScript, saved-search XML, and configuration object in a versioned repo your team can read and extend after the engagement ends.

The deal

The Fixed-Scope Model.

Engagements, not retainers — every Boldbard engagement has a fixed scope, fixed deliverables, and a fixed price, pinned before the first artifact is written.

Each engagement starts with a one-page statement of work. The deliverables are named. The acceptance test is written. The price is fixed. If those three do not move between signature and sign-off, no one argues about scope at the end of week two — the document was already the contract.

That trades the flexibility of a time-and-materials retainer for the absence of scope creep and the absence of a meter running against you. The cost of change becomes a conversation about the SOW, not an inference drawn from last week's timesheet. When scope does have to move, we re-sign a delta — never slide an open-ended allocation across the finish line.

The rhythm

Four steps, in order.

The order is fixed; the calendar is short. Most engagements ship inside of six weeks from kickoff to sign-off, with the build phase running on a two-week cadence.

Step 01

Discovery

A 30-minute call and a short written Q&A. We leave with the entities, the integrations, and the constraint that actually drives scope.

Step 02

Statement of work

A one-page SOW pins deliverables, a fixed price, and an acceptance test. Nothing ships until the document is signed.

Step 03

Build

Two-week build against the SOW. Every SuiteScript, saved search, and configuration ships behind a peer review on the client repo.

Step 04

Handoff

A walkthrough recording, a written operator runbook, and a thirty-day stabilization window. The repo is yours at sign-off.

What you keep

Versioned-Artifact Discipline.

Every SuiteScript, saved-search XML, configuration record, and integrator.io flow lives in a versioned repository on your Git host from day one. At handoff, your team can read every line and ship a change without us in the room.

Artifacts are committed behind a peer review on the engagement branch and merged onto your main through pull requests — the same discipline your own engineering team uses. The history is the changelog. Each commit message references the SOW section it delivers, so a controller who joins in month six can rebuild the original scope from git log alone.

Below is one of the artifacts from a recent engagement — a SuiteScript 2.1 scheduled script that rebuilds a saved search that an integrator had been hand-running each Monday. It is one of roughly forty files shipped under the same discipline.

artifact · sample

suitescript · 2.1 · user-event

/**
 * @NApiVersion 2.1
 * @NScriptType ScheduledScript
 * @NModuleScope SameAccount
 *
 * Rebuilds the "Open AR — by aging bucket" saved search on Monday at 06:00 PT.
 * Engagement 04 — delivery #11 of #14 (see SOW §3.4).
 */

define(['N/search', 'N/log', 'N/runtime'], (search, log, runtime) => {
  const TARGET_ID = 'customsearch_open_ar_aging';

  const execute = (ctx) => {
    const startedAt = new Date();
    log.audit('rebuild:start', { script: runtime.getCurrentScript().id });

    const s = search.load({ id: TARGET_ID });
    s.save(); // forced rebuild — every saved search needs this after column edits

    log.audit('rebuild:done', {
      ms: Date.now() - startedAt.getTime(),
    });
  };

  return { execute };
});

scripts/jobs/rebuild-saved-search.ts from engagement 04 — peer-reviewed, deployable, and in your repo. Every other SuiteScript, configuration record, and integrator export from the same engagement sits next to it under the same commit discipline.

Next step

Book a discovery call.

The first step of the rhythm is a 30-minute call and a short Q&A — no commitment, no meter running yet. Send a four-field note and we'll send a Calendly link back to your inbox inside a minute.