The small business automation consultant delivers one bespoke build. Fazm ships 17 of them, bundled in the .app.

On the SERP, the offer is uniform: diagnosis, a recommended stack (Zapier, Make, UiPath, n8n, custom GPTs), then a bespoke build that lives in the consultant's vendor account. The deliverable is usually a Zap or Make scenario, plus a short Loom video explaining it. The asset is intangible, billed hourly at $150 to $300, and tied to the platform. That is the default pattern every top-5 result for this keyword (theautomators.ai, aijourn.com, Automaly, smallbusinessautomationconsultant.com, IBM) is selling.

Fazm ships 17 automation skills inside the .app bundle, not as SaaS credits. On first launch, `SkillInstaller.swift` enumerates every file in `Resources/BundledSkills/` that ends in `.skill.md`, SHA-256 hashes each one via CryptoKit's `SHA256.hash`, and copies to `~/.claude/skills/<name>/SKILL.md`. On subsequent launches it re-hashes and only overwrites if the bundle has changed, so user-edited skills and app updates can coexist. The artifact is a plain markdown file you can read, copy, and version-control.

Personal: ai-browser-profile (sets up a persistent browser profile with saved logins). Productivity: telegram (send/read Telegram messages via the telethon API), google-workspace-setup (creates a personal OAuth app for Gmail/Drive/Calendar). Documents: pdf, docx, xlsx, pptx (read, write, convert). Creation: video-edit, frontend-design, canvas-design, doc-coauthoring. Research & Planning: deep-research, travel-planner, web-scraping. Social Media: social-autoposter (Reddit/X/LinkedIn/Moltbook), social-autoposter-setup. Discovery: find-skills (catalogs what is installed). Together they cover the span of workflows an SMB typically hires a consultant to bolt together for them.

Three practical reasons. First, no vendor account: the skill does not live in a tenant you do not own. Second, no licensing cliff: the hashed markdown is on your disk and survives a subscription lapse. Third, the skills execute against the macOS accessibility tree on your machine, via `AXUIElementCreateApplication` against the frontmost app. A consultant's Zap that relies on the HubSpot v3 REST API breaks when HubSpot deprecates v3. A skill file that asks Fazm to click the button labeled 'Save' in QuickBooks survives UI refreshes because the AX tree is role-indexed, not pixel-indexed.

Yes. Every bundled skill is shipped as an individual `.skill.md` file with YAML frontmatter. The installer is at `Desktop/Sources/SkillInstaller.swift` in the open-source Fazm desktop repo. The file defines `obsoleteSkills` (skills removed from a past release that get purged on launch), `categoryMap` (the 7 onboarding categories), `npmSkills` (a separate auto-update path for npm-backed skills like social-autoposter that runs `npm view <package> version` and upgrades when a newer version exists), and `analyticsProperties` (the telemetry shape that reports `installed_skills_count` and `bundled_skills_count` to PostHog). Every function is less than 100 lines.

Four cases keep a consultant in the picture. One, cross-team change management: if forty people in three departments disagree on the current-state process, you need a human to run interviews and broker buy-in. Two, compliance-signed workflows: SOX, HIPAA, or SOC 2 audits want a signed artifact and a named owner. Three, systems-of-record integrations with custom auth: if the process touches a bespoke ERP or a SAML-gated legacy app, a consultant may need to spec middleware. Four, process redesign: Fazm automates the process you describe, it does not decide whether that process should exist.

Two paths. Bundled skills update when the .app itself updates: on launch, SkillInstaller re-hashes every bundled `.skill.md`, and a hash mismatch triggers an overwrite and a toast ('Skill updated: <name>'). npm-backed skills (currently just social-autoposter) update asynchronously: SkillInstaller runs `npm view social-autoposter version`, compares to the installed `package.json`, and runs `npx --yes social-autoposter update` when the remote version is newer. That path lets frequently-changing skills ship out-of-band from the Mac app.

Count three things. Apps: how many apps does the process touch? Operators: how many people run it today? Audit risk: does the output need to be signed? If apps is five or fewer, operators is two or fewer, and audit risk is low, write a `.skill.md` and run Fazm. If any of those break, talk to a consultant. A typical SMB month-end close, invoice intake, vendor reconciliation, or weekly ops report falls in the self-serve bucket. Org-wide workflow redesigns do not.

Yes. The skill installer uses pure Swift + CryptoKit's SHA256 and FileManager APIs that ship on both architectures. The Fazm bundle itself is distributed as a universal binary (`x86_64-apple-macosx/release/Fazm_Fazm.bundle/BundledSkills/` is just the staging location for one architecture during the build). At runtime the skills run inside a Claude-backed agent that shells out to tools like `npm`, `jq`, and `curl`, and those are all arch-agnostic.

Only if the bundled version has also changed in a later release. SkillInstaller always re-hashes the bundled file and compares it against the installed file. If they match, the installer emits 'Skipped <name> (up to date)' and leaves your edited copy alone. If they differ, it overwrites — the assumption is that new bundled content is intentional and supersedes the installed one. If you want a permanent local-only variant, rename the directory in `~/.claude/skills/` or author a new skill with a different `name:` in the frontmatter.