MERISM
Engagements — Merism LLC

Fixed price. Fixed scope. Written down.

Most of the work is a build, or keeping a build running. Consulting is quoted the same way when that's the problem. Every engagement is a fixed price against a written scope — agreed before anything starts, and it does not move afterward. On-site work carries travel and per diem at cost. You will never sit through a call to be sold to: bring the work through the brief and a written scope with a price and a date comes back within two business days.

Build

Sites, apps, and internal tools — then the monthly upkeep if you want them kept running.

The studio's main work. Designed, built, shipped under your ownership — source, accounts, and infrastructure. A monthly retainer covers hosting, monitoring, and small changes so the thing does not go stale the week after handoff.

  • Web and application builds, design through infrastructure
  • Territory and field-team tools, including Territory Tracker as a standalone CRM
  • Dashboards and trackers for teams currently running on spreadsheets
  • Practical AI: agentic workflows and automation where it earns its keep
  • Lead capture wired into the system the field team already uses
  • Hosting, monitoring, maintenance, and a written monthly retainer

Quoted against a written scope, not off a menu. A build is a fixed price. A retainer is a separate monthly scope — 30 days' notice either way. Both land under your ownership. There is no hostage layer that forces you to stay.

Process and quality consulting is available when that's the actual problem. It is quoted the same way. It is not required to start a build.

Bring a build Ask about a retainer

Optimize

When the problem is the process, not a missing site.

Process, quality, and audit work from a studio with production-floor background — AQLs and in-process checks, both sides of an audit, tech transfers between lines and sites. Available. Not the front door.

These engagements are on-site. An audit means days on your floor watching the work as it actually happens, not a questionnaire. Scoping still runs in writing and you still won't sit through a sales call — but here the time on site is the deliverable you're buying. Quoted as a fixed engagement fee against a written scope, with travel and per diem billed separately at cost.

01 When you need the map first

Operations Audit

A written picture of how work actually moves through your business today — where it stalls, what that costs, and what to do about it in priority order.

Two weeks

Roughly one week on site, one in analysis and writing. Travel and per diem at cost. 50% to begin, 50% on delivery of the report.

  • Current-state process map built from observation, not org charts
  • Bottleneck analysis with the cost of leaving each one alone
  • Interviews with the people actually doing the work
  • Prioritized fix list, separating process changes from things needing a tool built
  • Written report you own and can hand to anyone
  • Credited in full against any engagement started within 90 days
02 Clock already running

483 Response & Remediation

You have fifteen business days and observations that need more than a promise. Investigation, root cause, written response, and a CAPA plan that survives the follow-up inspection.

Three weeks, expedited

Paced to the response deadline, not around it. Travel and per diem at cost. Scoped against the observations within 24 hours of your call.

  • On-site investigation and root cause for each observation
  • Written response drafted to the deadline, not around it
  • CAPA plan with owners, dates, and effectiveness checks
  • Commitment tracking so what you promised is what gets done
  • Readiness support ahead of the follow-up inspection
  • Optional: the tracking system to run it, built in-house
03 Before someone else looks

Quality Systems & Audit Readiness

Sampling plans, inspection criteria, and in-process checks that hold up when a customer, a registrar, or an investigator reads them — including standing in as SME during the inspection itself.

About four weeks

Varies with line and product count. Travel and per diem at cost. 50% to begin, 50% on handoff.

  • AQLs and sampling plans matched to actual risk and volume
  • In-process check points defined where they'll catch something
  • Inspection criteria written so two people reach the same call
  • SOPs and work instructions built around how the job is really done
  • Internal audit and gap assessment against your target standard
  • Subject-matter expert support during customer or regulatory inspections
  • Findings list with owners and dates, not a pile of observations
04 Highest variability

Tech Transfer & Deployment

Moving a process, product, or system to a new line, site, or platform without losing the thing that made it work in the first place.

Staged, multi-phase

Scoped as a sequence of funded stages with a written plan across them, so you approve one step at a time. Travel and per diem at cost.

  • Transfer plan with acceptance criteria agreed before anything moves
  • Documented current state so tribal knowledge doesn't stay tribal
  • Qualification and verification steps defined up front
  • Receiving-site training so the team can run it unaided
  • Post-transfer check-in window included

Develop

When the process is sound and the team isn't there yet.

Coaching, team development, and interim leadership — available when that's the work, not required to start a build. A fixed process handed to a team nobody developed is a fix with a shelf life.

These are session-based by nature. You cannot coach a supervisor over email. Scheduling is agreed once, up front, and then it's a standing cadence — no recurring negotiation, and still no meetings you didn't buy.

01 Per leader

Leadership Coaching

One-on-one development for a supervisor, lead, or manager you're betting on — the person whose next twelve months decide whether they grow into the role.

Monthly, per leader

Two 60-minute sessions a month plus async support, delivered remotely. No long-term contract — 30 days' notice either way.

Reduced rate for two or more leaders.

  • Two 60-minute sessions a month, scheduled on a standing slot
  • Async support between sessions — bring the hard conversation before you have it
  • Development plan written down and revisited, not improvised
  • Confidential by default; you get progress, not transcripts
  • Pause or stop with 30 days' notice
02 Whole crew

Team Development Program

A quarter of structured work with an intact team — building a crew that holds up when you're not in the building.

By the quarter

Fixed scope, including monthly on-site sessions. Travel and per diem at cost. 50% to begin, 50% at the midpoint. Renewable by quarter.

  • Baseline assessment of where the team actually is today
  • Monthly on-site or remote working sessions with the full crew
  • Training and work instructions matched to how the job is really done
  • Supervisor coaching folded in for whoever runs the team day to day
  • End-of-quarter written readout with what changed and what's next
03 Before you make the hire

Fractional Ops Leadership

Standing in as your operations or quality lead while you grow into affording the full-time role — carrying the function, not advising on it.

Monthly, ~1 day a week

Roughly one day a week, on site or remote as the role needs. Travel and per diem at cost. Monthly, no long-term contract — 30 days' notice either way.

Annual prepay available — two months free.

  • Named as the ops or quality lead, internally and to customers
  • Owns the metrics, the escalations, and the standing reviews
  • Develops your internal candidate toward taking the role over
  • Written handoff when you make the permanent hire — that's the goal, not a loss
  • Pause or stop with 30 days' notice

How an engagement runs

The same four steps every time, start to finish, entirely in writing.

01

Brief

You fill out the intake form. It asks the questions a discovery call would, and you answer them when it suits you.

02

Scope

Within two business days you get a written scope: what gets built, what it costs, when it lands, and what's explicitly out.

03

Work

Starts on deposit — building, auditing, or sitting with your team, depending on the track. Progress is visible in a shared tracker you can check any hour without asking anyone.

04

Handoff

Delivered, documented, and handed over — code deployed, findings written up, or a team that can run it unaided. Support continues on any recurring plan.

Everything above happens over email and a shared tracker. If your organization requires a call to approve vendors, we're likely not the right fit — and that's worth knowing on day one rather than week three.

The details, before you ask

The things that usually take a call to establish, established here instead.

Why no sales calls?

Written scope is better scope. A call produces a shared memory that two people recall differently; a document produces a thing you can both point at in week six. It also means the studio spends its hours working rather than scheduling.

To be clear about the distinction: no call is required to scope, quote, or approve anything. But the Optimize and Develop tracks involve real time with your people — an audit means hours on your floor, coaching means sitting with a supervisor. That time is the deliverable you're buying, and it's priced in. What you'll never get is a meeting whose purpose is to sell you something.

What about travel and per diem?

Every engagement is quoted as a fixed price against a written scope, so the number does not move once it is agreed. Travel, lodging, and per diem are billed separately at cost, estimated in the written scope before anything starts and reconciled against receipts — never marked up. Remote work carries no travel cost, and where an engagement can be done remotely without weakening it, it is.

How do payments work?

50% deposit to start a sprint or deployment, 50% on handoff. Recurring plans bill monthly in advance, or annually if you'd rather prepay — a prepaid year runs ten months' cost instead of twelve, and it's refunded pro rata if you stop early. Invoices are sent by email with card and ACH options.

What if the scope is wrong?

The written scope is the contract. If something material was missed, it becomes a documented change with its own price and date — never a silent addition, and never an argument about what was said.

Who owns the work?

You do, on final payment. Source code, accounts, and infrastructure are yours and deployed under your ownership. There's no hostage layer that forces you to stay.

What isn't offered?

No hourly billing, no staff augmentation, no sitting in on your internal meetings as a spectator, and no work scoped verbally. Fractional Ops Leadership is the exception on meetings — carrying the function means being in the reviews that come with it.

What if it's bigger than a sprint?

Larger builds are quoted as a sequence of sprints with a written plan across them, so you're approving one funded step at a time rather than a single large unknown.

Bring the work. Get a scope back.

The intake form takes about five minutes. A written scope with a price and a date comes back within two business days.

Start a project