Public GitHub cadence and hard numbers first — then the offers. No borrowed authority; if the graph is thin, that shows here too.
7-day refund, no questions asked. Refund policy.
No subscriptions, no retainers. Every purchase is a one-time lump sum. You own what you buy.
The playbook is a PDF. The power pack is a full template repo you get access to. Pair sessions include all artefacts produced during the session.
Have a specific setup to wire — want an operator on a call to get it done.
Playbookif you're self-implementing and want the written method. Power Pack if you want templates plus a written guide. Pair-engineering session if you want hands-on wiring with me. Send a briefif you're unsure — I 'll point you at the right tier.
Most sessions ship within 1–2 business days of kickoff. Tight-scope blocks often land same-day. Digital products (guides, template repos) are immediate downloads.
Speed comes from the async-first model: written briefs in, written deliverables out, no scheduling overhead.
Yes— digital products (guides, power packs) carry a 7-day refund as long as you haven't read the guide or started the session hours yet. Just email and it's done.
Pair-engineering hours are non-refundable once consumed; unconsumed hours within an un-started block can be refunded on request within 30 days of purchase.
Pacific Time. Written guides and digital products are async-first — you send a brief, you get a deliverable, no standing calls.
Pair-engineering blocks are scheduled live sessions when you book them; we coordinate times in Pacific and stay async between sessions when that fits.
No retainers, no SLAs on the core product line. Pair-engineering clients get a stated turnaround at booking (typically 24–48 hours for standard sessions). If scope shifts mid-engagement, we agree in writing before any additional hours run.
No babysitting post-delivery. No hosted SaaS — deliverables are yours to run. No subscriptions on the core product. No fractional-CTO or standing retainer arrangements. No broad architecture consulting outside a booked pair-engineering session.
The scope is sharp by design.
Yes, materials are client-agnostic. Most examples reference Claude Codebecause it's my primary daily driver, but patterns translate. Pair-engineering sessions can use whichever client you prefer.
No for written guides and Power Packs (you apply them yourself). Yes for pair-engineering if you want me to operate inside it — read-only collaborator access during the session; revoked after. NDA on request.
Yes. Mutual NDA available on request before any pair-engineering session or buyer-bot install. Standard 2-year term. Send a brief to start.
Invoicing through Albino Geek Services Ltd. Comfortable contracting with Canada, US, EU, UK, AU, NZ buyers. Other jurisdictions case-by-case (tax/compliance reasons).
One email when something ships. No spam, no upsells.
Not ready to subscribe? Read the free Playbook Preview first — the table of contents and chapter one. No signup.
Damon Blais
Operator, Albino Geek Services Ltd.Contribution activity — last 12 months