A clear plan. A short build. Your team, running it.

Every Boldbard project runs on the same operating model — a clear plan pinned before any code is written, a four-step rhythm from discovery to handoff, and a discipline that keeps every SuiteScript, saved search, and config record in a versioned repo your team can read and extend after we leave.

The deal

A clear plan with a defined finish line.

Before we write code, we agree on what “done” looks like — and what it costs. If we can’t put both on a single page, we’re not the right fit.

Every project starts with a one-page plan. The deliverables are named. What “done” looks like is written. The price is fixed. If those three do not move between signature and handoff, no one argues about scope at week six — the document was already the contract.

That trades the flexibility of paying by the hour for the absence of scope quietly growing — and the absence of a meter running against you. The cost of any change becomes a conversation about the plan, not an inference drawn from last week's timesheet. When scope does have to move, you sign a new short addendum — we 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 projects ship inside of six weeks from kickoff to handoff, with the build running on a two-week cadence.

Step 01

Discovery call

A 30-minute call and a short Q&A. We leave with the entities in scope, the integrations, and the gap that’s actually driving the move.

Step 02

The plan

A one-page plan pins the deliverables, the price, and what “done” looks like. Nothing ships until the plan is signed.

Step 03

Build

A short build against the plan. Every SuiteScript, saved search, and config ships behind a peer review on your repo.

Step 04

Handoff

A walkthrough recording, a written runbook, and a support window after go-live. The repo is yours at handoff.

What you keep

Trained teams, not just built systems.

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

Artifacts are committed behind a peer review on the project 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 plan section it delivers, so a controller who joins in month six can rebuild the original scope from git log alone.

That means your team isn't dependent on us after we leave. The result of the build is a codebase they can run, change, and ship from — built by yours, not held hostage by a partner login. Below: one of the artifacts from a recent light- manufacturing project — a SuiteScript 2.1 schedulable that rebuilds a saved search that an integrator had been hand-running each Monday.

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 a recent build — peer-reviewed, deployable, and in your repo. Every other SuiteScript, configuration record, and Celigo export from the same project sits next to it under the same commit discipline.

Next step

Book a 30-minute call.

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

Book a 30-minute call See what we build