Workshop · accepting briefsCycle 04
00:00:00 UTC
§ 01 — Brief What we can do for you

Five practices.
One workshop.
Whatever your business actually needs.

Engagements rarely fit in one box. Most of our work weaves two or three of the practices below into a single, coherent system. Browse — then call.

Brochure sites are a solved problem. We build the other kind — sites that take bookings, sell things, capture leads, and connect to the rest of your operation.

Typical deliverables

  • Marketing sitesAstro / Next / clean HTML, performance-budgeted, edge-cached.
  • Booking & orderingStripe checkout, Cal.com / custom calendars, SMS confirmation flows.
  • Backend-connected sitesForms that go somewhere useful — CRM, Sheets, Slack, your inbox.
  • Performance & SEO99-Lighthouse builds, structured data, meta + sitemap discipline.
Stack we reach for

Astro · Next.js · Tailwind · Stripe · Resend · Cal.com · Cloudflare

Typical timeline

2 – 5 weeks · single operator · weekly demo

When the spreadsheet stops working and the off-the-shelf SaaS doesn't quite fit, we build the missing tool. Lean. Owned by you. Documented in plain English.

Typical deliverables

  • Internal dashboardsOperational views your team actually opens — not the one IT made.
  • Workflow automationsMulti-step processes turned into one button. Approvals, queues, retries.
  • Lightweight CRMsA single tab that holds your whole client world — not Salesforce.
  • API integrationsSlack, Google Workspace, QuickBooks, Stripe, Linear — wired together.
Stack we reach for

Python · Next.js · Postgres · Drizzle · tRPC · Inngest · Auth.js · Resend · Hugo · Astro · Eleventy · Jekyll

Typical timeline

4 – 10 weeks · MVP first, then iteration

We've watched a lot of "AI transformations" produce slide decks and not much else. Our work is the opposite — narrow, measurable wins that pay back inside a quarter.

Typical deliverables

  • Repetitive task automationAnything you do five times a week the same way is on the list.
  • Reports & summariesMonday digests, weekly briefings, customer-call recaps.
  • AI-assisted workflowsSlack synthesis, Jira reporting, calendar shaping, draft replies.
  • Local-first & cost-efficientWhen the data is sensitive or the bill matters, we'll go local.
Models & tools we use

Claude · GPT-4o · Gemini · Llama (local) · Ollama · Inngest

Typical timeline

2 – 6 weeks · pilot first, scale only if it pays

We come from the world of Kubernetes clusters and CI matrices. We use that experience to not over-engineer your business. Sometimes the right answer is a $12 VPS and a quiet pipeline.

Typical deliverables

  • Container deploymentsKubernetes when the load demands it. Docker Compose when it doesn't.
  • CI / CD pipelinesGitHub Actions, GitLab — deploys you trust, rollbacks you've tested.
  • Infrastructure as CodeTerraform, Ansible, Packer — your infrastructure, in version control.
  • Cloud cost designArchitecture reviews that often reduce your monthly bill significantly.
Stack we reach for

AWS · Cloudflare · Hetzner · Terraform · Ansible · GitHub Actions

Typical timeline

1 – 4 weeks · audit · plan · migrate

The most valuable thing we do — and the least glamorous — is connect the eight tools you already pay for so you stop doing the same thing in three places.

Typical deliverables

  • PaymentsStripe, Square, PayPal — wired into invoicing, accounting, and your inbox.
  • Email & domainsCloudflare, Google Workspace — DNS, SPF, DKIM, the boring critical bits.
  • Booking & invoicingCal.com, Stripe Invoices, QuickBooks — connected, not copy-pasted.
  • Tool-to-tool automationWhen a customer pays, the right thing happens in the other six tools.
Tools we wire

Stripe · Square · Cloudflare · Google Workspace · QuickBooks · Cal.com

Typical timeline

1 – 3 weeks · audit · stitch · automate

Begin

Tell us where it hurts.
We'll tell you if we can help.

Open a brief No deck. Just a conversation.