Four focus areas: AI, SEO + GEO, marketing automation, Agentic OS. Five engagement shapes: free scoping call, Audit, Sprint, Custom, Ops Retainer. Quote on scope. Written within 24 hrs of the call.
Each shape is productized: fixed scope, fixed deliverables, written quote before signing. Scoping Call is the entry (free, 30 min). Audit when you don't know where AI fits yet. Sprint when the workflow fits in one sentence. Custom for anything multi-workflow. Ops Retainer for ongoing maintenance and tuning of systems already shipped. Every paid shape is quoted on scope, no surprises.
The starting point. We walk through one workflow, sharpen scope, decide which of the three paid shapes fits. Free.
If none does, I'll say so on the call and send you to who or what's better.
A focused week of three founder interviews and a workflow review. The goal is to find the three to five places where AI, SEO, or automation returns measurable time, and turn them into a ranked 30-day plan.
The deliverable is a written report with a prioritized opportunity list, vendor recommendations, monthly cost projections, and milestone-level implementation steps.
Right fit when AI placement is unclear, or previous tools haven't stuck.
A productized build with a fixed scope and fixed delivery window. The workflow is agreed at signing, then deployed and documented by the end of the sprint.
The workflow has to fit in one sentence, for example, "send a summary of yesterday's sign-ups to my inbox at 6am every weekday." If it can't, a Custom build is the right shape instead.
Common scopes: daily operational brief, weekly metrics report, sales follow-up automation, content cross-poster, AI-assisted inbox triage.
For builds that exceed the scope of a Sprint. The engagement opens with the free scoping call and a written spec plus quote within 24 hours. Milestone-paid, with progress updates throughout and a demo at each milestone.
Reference engagement: CISNET marketing site rebuild. Next.js 16 migration, 200+ programmatic SEO pages, Facebook Lead Ads pipeline, custom admin portal. Three months, solo, shipped Q4 2025.
Custom is the right shape for any scope that doesn't fit cleanly into one of the productized engagements above.
A monthly engagement for clients whose systems I've already shipped. The retainer is structured around specific deliverables, not general access. Every hour goes against monitoring, prompt and eval maintenance, on-call response, or minor enhancements.
Two tiers depending on system size. Both have a capped monthly hour budget that resets monthly and doesn't roll over. Cancellable any month with 30 days' notice.
Engagement rule: never sold cold. Only available after an Audit, Sprint, or Custom build has shipped.
Three concrete subtypes. If you recognize yourself here, the engagement is built for you.
$200K-$3M ARR, 1-8 people. The team is technical but needs workflows shipped, onboarding sequences, billing webhook handlers, AI-augmented features, internal ops automation.
5-20 people, founder-led, $1-5M revenue. Common engagements: internal tooling, creative-variant generators, client lead pipelines, white-label dashboards, content production engines.
Small teams with technical leadership and no procurement cycle. Marketing sites, lead-pipeline infrastructure, custom admin portals, programmatic SEO surfaces. CISNET is the reference case.
Real workflows. Each ships as a 3-day Sprint or gets customized to your stack. If a build isn't here, it lives in Custom.
One source article → 6+ platform variants. X thread, LinkedIn carousel, newsletter, video script, Reddit, podcast intro. RSS-triggered. AI-drafted. You approve before ship.
Whop webhook (or Stripe / Lemon Squeezy) → Claude personalizes welcome → tags subscriber → triggers Day-0 to Day-30 sequence. Wired on the AOF stack.
06:00 ET summary in your inbox. Stalled deals. Urgent items. Today's priorities. Metrics movement. Pulls from CRM + calendar + email. AI flags what matters.
Scans 6+ competitors across pricing pages, launch blogs, X, changelogs. Flags pricing changes and launches. Weekly intel report drafted Sunday night. Lands in your inbox Monday morning.
Install and configure Claude Code for your whole team. Custom CLAUDE.md, sub-agents, hooks, MCP servers tuned to your stack. Training + cheatsheet included.
Apply a unified design language to your existing app. Token system. Component patterns. Voice rules. Audit + migration plan included. Built on Terminal DS or your brand.
Full community workspace. Whop, Skool, or custom on your stack. Member auth. Gated content. Weekly drop cadence. AI coach. Automated onboarding. Reference: AIOpsForge.
Schema markup. JSON-LD. Per-page OG images. Sitemap. Robots. FAQ schema, llms.txt for AI-search engines. Built to rank in Google, Perplexity, and ChatGPT search.
Landing page + gated PDF → Beehiiv, Kit, or ConvertKit → tagged + sequenced. AI personalizes follow-ups. Stripe or Whop checkout wired in. Plausible analytics + funnel tracking.
Custom Model Context Protocol server. Connects Claude to your internal tools, data, or APIs as first-class actions. Examples: Notion-MCP, Linear-MCP, your-CRM-MCP.
One brief → N image and copy variants for an ad set. Brand-tone guardrails baked in. Approve, reject, regenerate. Built for agencies running paid creative at volume.
If yours isn't here, ask on the call.
Every paid engagement is quoted on scope after the free 30-minute scoping call. The written quote lands inside 24 hours. deliverables, milestones, timeline, total price. Once you accept it and sign, the price is locked; productized scope keeps it from moving. Audit and Sprint are paid 50% on signing and 50% at delivery. Custom builds are milestone-paid against a staged schedule. Ops Retainer is monthly, cancellable with 30 days' notice. No hourly billing, no surprise invoices.
My default stack is Claude Code for development, Vercel for hosting + serverless + cron, Anthropic API for the AI layer, and Supabase for Postgres + auth + RLS. Around that: TypeScript, Next.js, Tailwind v4, Resend for transactional email, Stripe for payments, Plausible for analytics. I'll work in your stack if it's modern. Next.js, Astro, Django, Rails, Laravel, FastAPI, Postgres are all in scope. I won't build on n8n, Make, or Zapier as the primary execution layer: they're fragile under load, expensive past 5K events/mo, and the visual graph becomes unreadable to anyone who joins the team after I leave.
You. Outright. Every engagement is work-for-hire under a written agreement. At the close you receive the full source code, the deployment access, every environment variable, every account credential, and the right to modify, extend, or sell the work without restriction. I retain no IP, no licensing rights, no royalty claims. If you stop working with me tomorrow, the system keeps running on infrastructure that's already in your name.
Hourly billing aligns nobody's incentives correctly. The consultant earns more by taking longer. The client earns peace of mind only by watching the clock. Both sides end up optimizing for the wrong thing. Fixed-price flips it: I'm incentivized to ship efficiently because overrun eats my margin, and you're incentivized to give clear feedback because every approved milestone gets you closer to the deliverable. The outcome, a working production system, is what we both want, and fixed-price is the only structure that lets us both focus on it.
I'm based in Toronto on Eastern Time. Most communication is async by default: a shared Slack channel or email thread plus a recorded Loom walkthrough at each milestone. That keeps timezone gaps from blocking progress. Live calls happen at kickoff, milestone demos, and the closing retro. I'll book those in your timezone if it falls between 9am and 9pm Toronto time. If we're more than 8 hours apart, the engagement runs entirely in writing plus Loom updates, which most clients prefer anyway.
Sprints are productized fixed-scope builds, the scope is locked at the spec stage and the engagement ends at the agreed deliverable. If you realize you need more, it becomes a separate Sprint quoted at the close of the first. Audits and Custom builds are more flexible: anything outside the written spec gets a new written quote with a new timeline and price, surfaced as a change-order before any work happens. I won't silently absorb extra scope to keep the relationship pleasant, that ends in burnout for me and a quietly delayed deliverable for you.
Sprints can usually start within 5-7 days of signing, the scoping is fast because the shape is productized. Custom builds depend on current capacity: sometimes within a week, more often 2-3 weeks out so I can write a real spec first. Audits book 2-3 weeks out because they require three founder interviews and structured deep-dive time. The fastest path to a real answer on timing is the free 30-minute scoping call. I'll quote both price and earliest start date in the written quote inside 24 hours.
Book the call anyway. The free 30 minutes is structured around figuring out what's actually broken, not selling you on a specific shape. If AI isn't the right fix, if the real problem is positioning, sales process, hiring, or simply that your existing tool is fine. I'll say so on the call and recommend who or what is a better next step. About 1 in 5 scoping calls ends with "don't hire me, hire X instead." That's intended, not a failure mode.