Sitemap

Start with c0nsl for the scoped build, Clone to automate the back office, and claude-meter on every laptop that talks to the agents. You are the clearest-cut SMB match for this list and the one with the lowest friction to production.

Start with n8n. Self-host the Community edition, build one workflow, and only consider Cloud or Make.com if self-hosting becomes a chore. The audit-and-fork motion is the cheapest insurance against vendor lock-in this category sells.

Every page on c0nsl, grouped by section.

After a build, a long-running shell command, a pause and resume, or any teammate push: Read the file again before the next Edit. The Edit tool

The single largest multiplier. One workflow, a multi-step system, and an organization-wide rollout are three different orders of magnitude, not three points on a line. Most small-business work is a single workflow or a small system. If a quote sounds like a transformation, the scope has drifted, and the price drifted with it.

Does the upstream system expose a documented HTTP or webhook surface?

Open one in a private window, view source, and look for the actual content in the initial HTML response. If it is there, tier one is enough and the rest of the ladder is overhead. Marketing sites built on Astro, Next.js with server components, or any static site generator usually qualify. SPAs with a single empty mount node do not.

30 or 60 minutes, $75 published rate. I read the existing repo (or a shared diff), name three concrete automations ranked by hours saved per week, and identify which of the four files are missing or wrong. The output is a fixed-scope quote inside 48 hours mapped to one of the published tiers.

Guides for SMBs on AI automation, security cameras, property management workflows, and open-source tools.

n8n self-hosted is the default. Make and Zapier fill the connector gaps. Lindy and Relevance fit narrow agent-style cases. The SVC-008 AI Stack Selection audit ends with a one-line recommendation per workflow, not a tool tier list. Pick this layer first because it sets the shape of every other layer.

Anthropic bills API usage out of prepaid credits. VAT is applied when you buy the credits, not when the model runs. If the organization has no VAT ID on file, you pay the local rate at the moment of top-up. A $1,000 credit purchase in Hungary becomes a $1,270 card charge. That money is out the door before a single token has been processed.

Not the calls, the things a human does after the calls. Tag this CRM record, draft this email, flag this for legal, route this ticket. One row per task.

On a senior engineer running real per-engagement architecture (a committed plan file, a scratch folder for load-bearing facts, a per-repo writers manifest), three to five active engagements is the sustainable ceiling.

The customer is already angry, the order context is incomplete, and the legal exposure is non-trivial. An AI agent that auto-issues a refund inside the wrong policy line burns trust faster than a delayed human reply does. Keep this routed to a person, log everything the AI saw, let the human pick the resolution.

$0.99 per resolved outcome. No seat fees. Outcome-based.

Open the target window with the right inspector (DevTools accessibility pane, AX dump, Inspect.exe). If every interactive element has a stable role and accessible name, the workflow is tree-bindable. If half the buttons are unnamed, the build starts with naming them or with a different surface.