LightCube Labs automation

Turn the work your team repeats every week into an AI system that runs in your own accounts.

For small B2B teams, especially seed to Series A AI and developer tool companies, whose product moves faster than their content and operations. Pick a free template, a template pack, a fixed-price build or a monthly system. Every step happens in writing, on your schedule.

Get the free templatesStart a $2,500 build with the written intake

Free templates / $29 and $99 template packs / $2,500 fixed-scope build / $1,500 per month system

Four steps. All in writing.

  1. Tell us the workflow. Fill in a written intake form, about 20 questions. You describe what happens today, step by step, which tools are involved and what "working" would mean.
  2. Get a written scope. You receive a one-page scope with the exact deliverables, the acceptance tests and the start date, or a short note saying a template or a different tool fits better.
  3. We build in your accounts. You create the access we list, in your own tools. We build, test on your real records with sending switched off, and post written progress updates.
  4. You get a written handover. Workflow export, setup and run guide, prompt files, test log and a troubleshooting sheet. Questions and changes go through one shared written thread.

There is nothing to schedule. You reply when it suits you, and every decision is written down so anyone on your team can pick it up later.

What you get, per tier

Free templates

$0, email required

For teams that want to see how we build before spending anything.

  • 3 starter n8n workflows (export files you import into your own n8n)
  • A README for each: what it does, which accounts it needs, a setup checklist, a sample input and the expected output
  • A placeholder for every key or credential, so nothing secret ships with the file
  • Occasional emails with new templates. Unsubscribe in one click.

Occasional emails with new templates. Unsubscribe in one click.

Template packs, $29 and $99

For teams with someone technical enough to import a workflow and follow a written guide.

$29 Starter Workflow Pack (5 workflows)

  • 5 importable n8n workflows for jobs small B2B teams repeat every week: inbound lead enrichment and routing, support triage with draft replies, release notes drafting, content repurposing, weekly metrics digest
  • Prompt files you can edit, kept separate from the workflow
  • Numbered setup guide for each workflow, plus sample input and expected output to test with before you connect real accounts
  • A shared failure alert workflow and a "which workflow first" sheet
  • A human approval step before anything is sent or published
Starter Workflow Pack $29

$99 Pro Workflow Pack (14 workflows)

  • The 5 Starter workflows plus 9 more: CRM hygiene report, invoice and receipt capture, competitor page change monitor, customer feedback tagging, inbox triage, content brief builder, stale deal nudges, brand mention monitor, weekly engineering digest
  • A "which workflow first" decision sheet for all 14
  • A written guide to chaining the workflows into one system
  • Updated versions of the included workflows when we release them (no fixed update schedule)
Pro Workflow Pack (14 workflows) $99

Packs are self-serve. Written email support covers setup questions about the files themselves, not custom changes. Custom changes are what the build is for.

Fixed-scope build, $2,500

For teams that want one system built, tested and handed over, without managing the build themselves.

Delivery: dates are set in the written scope. Work starts once the scope is accepted, payment is received and all listed access works.

You get:

  1. A written one-page scope and build plan before any work starts
  2. One automation system built in your own accounts: 1 trigger source, up to 3 connected tools, up to 2 AI steps (drafting, summarizing, classifying or extracting), and one output destination
  3. Human approval step wherever the system would publish, send or change a customer record
  4. Error handling, retries and a failure alert to a channel you choose
  5. Tests on up to 25 of your real records with sending switched off, plus a written test log
  6. Prompt files with notes on what each instruction controls
  7. Two rounds of written revisions inside the build window
  8. Handover pack: workflow export, setup and run guide, credential map (names and owners only, never the secrets), troubleshooting sheet, and a "how to change it yourself" guide for the edits teams make most
  9. A fix period after handover, set in the scope, for anything that does not meet the agreed acceptance tests

Every build also includes:

  • Your accounts, your credentials, your keys. You pay tool and AI usage directly to each provider.
  • You own the workflow, the prompts and the docs from handover.
  • Written progress updates.
Start with the written intake

Monthly system, $1,500 per month

For teams that want the system run, watched and extended every month, with no hiring.

Starts: after a $2,500 build, or after we take over and document a workflow you already have (scoped in writing first).

Each month you get:

  1. Monitoring of the systems we built or documented for you, with written fixes when something breaks
  2. One new small automation or one major change to an existing one (same size limits as the build tier)
  3. Up to 8 small written change requests (copy edits, a new field, a changed schedule, a new recipient)
  4. A monthly written report: what ran, what failed and how it was fixed, what changed, and a ranked list of next automations
  5. Written replies to your requests by email

Not included: building in accounts you do not own, new tools or platforms beyond the agreed stack, paid ads, posting without written approval, work outside the monthly cap (quoted separately in writing).

Terms: month to month. Cancel in writing before the next billing date; the next month is not billed and everything we built stays in your accounts.

Ask about the monthly system

Example automations

Examples of what we build. These are illustrations of workflow shape, not client results. We do not publish client outcomes on this page.

Example 1. Changelog to social thread drafts

Input
your release notes RSS feed or changelog page
Steps
new entry detected, AI drafts a thread in your voice using your style notes, draft goes to a review doc or channel
Output
one ready-to-edit thread per release
What stays human
approving and posting
Available as
fixed-scope build

Example 2. Product docs to weekly newsletter draft

Input
docs pages and merged release notes from the past 7 days
Steps
collect changes, AI groups them into 3 to 5 reader-facing items, formats a newsletter draft with links
Output
a draft in your email tool or a shared doc every Monday
What stays human
subject line choice and the send button
Available as
fixed-scope build

Example 3. Daily sales digest from Stripe or Gumroad

Input
yesterday's orders from your payment or storefront account
Steps
pull orders, summarize by product and source, flag anything unusual against the prior 7 days
Output
a short written digest in email or chat each morning
What stays human
deciding what to do about it
Available as
fixed-scope build

Example 4. Inbound lead triage

Input
website form or shared inbox
Steps
AI classifies each message (sales, support, partnership, spam), enriches with public company info, drafts a first reply
Output
a sorted queue with draft replies, logged to your CRM or sheet
What stays human
sending replies and any pricing decisions
Available as
fixed-scope build

Example 5. Support question to FAQ draft

Input
resolved support threads from the past week
Steps
AI finds repeated questions with no help article, drafts new FAQ entries with source links
Output
a weekly list of draft entries for review
What stays human
approving and publishing
Available as
fixed-scope build or monthly system

Process (fixed-scope build)

The build starts when the scope is accepted, payment is received and all access in the scope works. The written scope sets the dates.

  1. Intake and scope: you submit the intake form. You get the written scope and start date, or a written note that a template fits better. We'll reply by email.
  2. Access check: we confirm every login works and read sample records. Surprises in the data are flagged in writing now, not on handover day.
  3. Build: we build in your accounts and post written progress updates.
  4. Tests: tests on your real records with sending switched off. You get the test log and revision round 1.
  5. Revision and go-live decision: revision round 2 and your written go or no-go on going live.
  6. Handover: handover pack delivered. The system is yours.
  7. Fix period: fixes for anything that does not meet the acceptance tests, for the period set in the scope.

The step that moves dates is almost always access. The intake form lists exactly what we will need, so you can set it up before the build starts.

Ownership and costs

  • Everything is built in accounts you own. If you stop working with us, it keeps running.
  • Credentials are created by you, in your accounts. We never ask you to paste a password or key into email or a form.
  • Tool subscriptions and AI usage are billed to you directly by each provider. The scope estimates them before you commit.
  • Larger changes after handover are a new fixed quote in writing. Small edits are covered in the "change it yourself" guide.

FAQ

Will we ever need to talk live?
No. Intake, scoping, updates, reviews and handover all happen in writing. You reply when it suits your team, and there is a written record of every decision.
How do you scope without a live session?
The intake form asks for the workflow step by step, the tools, volumes, data rules and what success looks like. If something is unclear we send written follow-up questions, usually 3 to 5, before the scope.
What does "fixed scope" mean here?
The scope lists the trigger, the tools, the AI steps, the output and the acceptance tests. The price covers exactly that. Anything new becomes a written change request with its own price, and nothing starts until you approve it in writing.
What if our workflow is bigger than one build?
We split it into stages and scope the first one. Each stage is its own fixed price. Or the monthly system adds one new automation each month.
Which tools do you build with?
Mostly n8n, Make, Zapier, Claude Code scripts and MCP servers, plus the APIs of the tools you already use. We pick the simplest option your team can maintain, and say so if a native feature already does the job.
Will this save us a set number of hours or bring in revenue?
We cannot promise that. We commit to the deliverables and acceptance tests in the written scope. Results depend on your process, data and how you use the system.
Who owns the work?
You do, from handover. The workflow exports, prompts and docs are yours. We may reuse general techniques, never your data or your business details.
What data do you need, and how is it handled?
Only the access listed in the scope, through accounts you control and can revoke. Tests run on a sample of your records with sending switched off. Tell us in the intake if any data is regulated or sensitive, and we will scope around it or recommend not automating that part.
Do the AI steps post or send things on their own?
Only if you ask for that in writing. By default, anything that publishes, sends or changes a customer record waits for a human approval step.
Do you work with teams outside the US?
Yes, if you can work in written English and pay in USD.
How do we pay?
By invoice from LightCube Labs. Payment terms are in the scope before you accept it.
Can we try your work before a build?
Yes. Start with the free templates or a template pack. They are built the same way our client systems are.
How do we stop the monthly system?
Tell us in writing before the next billing date. The next month is not billed, and everything stays in your accounts.

Start with what fits your team today.

Every step happens in writing. We'll reply by email.

The LightCube Labs team