Skip to main content

Service

Installed and tuned

A pack installed and tuned in your stack over one to two weeks.

By
Caleb and Ryan, the founders
Updated
August 28, 2026
Version
1.0, in the library
  • n8n
  • Make
  • Claude Code
  • Anthropic API

The mini project. We take a pack, put it into your systems, run it against your real data for a week, and tune it until the receipts are clean. Scope agreed before we start.

Built, documented, running.

Part of the working library we deploy from on every engagement.

Bring this into a project

Runs on

  • n8n
  • Make
  • Claude Code
  • Anthropic API

3 requirements and 3 install steps, below.

  • Complete and documented: the same files we run ourselves.
  • Deployed and tuned to your stack as part of an engagement.

What it looks like

Draft excerpt
# Operating guide: invoice chase ## What runs whenDaily at 07:00 in your timezone: the ledger check and any reminders due. ## What to look at weeklyThe receipts folder: one file per run, what was sent, what stopped, why. ## If something looks wrongTurn sending off with the switch in the workflow. Then call us.

How it goes

3 items. Includes deployment guide.

  • Week oneInstall, connect, run on real data, read every receipt.
  • Week twoTune the rules, the thresholds and the messages; hand over with the guide.
  • The guideYour operating guide: what runs when, what to check, who to call.

Who it is for

  • You want the outcome on the card without doing the install.
  • Your stack is your own: a custom CRM, an old ERP, a document type nobody else has.
  • You are deciding whether to hire us for the bigger build and want a small one first.

Requirements

  • A pack, or a recipe from the eight
  • Admin access to the systems involved
  • One person on your side who owns it afterwards

How to book

  1. 01

    Tell us the pack and the stack; we quote a fixed number inside the band.

  2. 02

    One kickoff call, then we work in your systems for a week.

  3. 03

    One handover call with the guide.

Where this sits

  1. This system

    Installed and tuned

    In the library, running.

  2. In your stack

    Deployed on an engagement

    The audit finds which system earns its place first; we install and tune it around how you work.

Questions

Is the scope really fixed?
Yes. What gets installed is agreed before we start and does not move. That is the law across everything we do.
How long does it take?
One to two weeks: installed in your stack and tuned around how you work.
How is this different from a project?
Scope. Installed is one pack in your stack. A project is a system built for you; the engagement details are on the Guide page.
Can we do it without a pack?
If one of the eight recipes is what you need, yes; the pack is just the head start.

Changelog

  1. August 28, 2026In the library. Version 1.0 runs in our own operation.

Related

  1. CLAUDE.md starter

    Company brain starter

    Give an agent the shape of your company before it writes a word

    Works with Claude Code, Cursor.

    Built and running

  2. Skill

    Inbox triage skill

    Every morning's inbox sorted into reply, delegate, file and ignore, with the drafts written

    Works with Claude Code, Cursor.

    Built and running

  3. Workflow

    Competitor watch to Slack

    Every Monday, what your competitors changed last week, in one Slack message

    Works with n8n, Anthropic API.

    Built and running