ctlyst — software that ships.

// manifest · five lines

^[3]hover a row. no icons.

01 —webnext.js· typescript· edge· deployed yesterday2–6 wks

▸

marketing sites, product surfaces, internal tools. I write the types, set the budget, ship to staging on day three. if the page takes longer than 1.1s to TTI, it doesn't leave. no cms unless you actually need one.

last 3: harbor.fm · northbeam/admin · stride/console

02 —mobilereact native· expo· offline-first· ships to stores6–12 wks

▸

expo + react native, swift/kotlin when it matters. offline-first state, gestures that feel right, submissions that pass on the first try. I bring my own crash reporter.

last 2: fieldwise · ios/android · column/mfg pocket

03 —cloudaws· k8s· terraform· infra you can actually debug2 wks — ∞

▸

IaC, CI/CD, observability, cost audits, migrations that don't burn a weekend. I leave behind runbooks a human can read, not 400 tickets in a backlog. no lock-in.

last: stride · migrated vercel → fly · cut bill 63%

04 —aillms· agents· workflows that replace a teammate3 wks pilot

▸

rag pipelines, agentic workflows, ops automation. evaluation-first. we measure before we ship. no demos that die on a tuesday. if the llm isn't the right tool, i'll tell you and charge less.

last: harbor · triage agent · resolved 38% of tickets unassisted

05 —wordscopywriting· technical seo· landing pages that convert1–3 wks

▸

the non-technical bit: copy, structure, seo. I write your landing page, your docs, your product copy. schema, metadata, sitemaps, core-web-vitals in the green. if your hero says “passionate about crafting,” I'll fix it.

last: column · homepage rewrite · organic signups +2.4×

// process · the whole section

^[4]this is the flex.

talk→

01 · intakeone call, one doc. no sales deck.

scope→

02 · fixed scopeweekly demos. usually 2–8 weeks.

build→

03 · no lock-incode is yours day one. no retainers.

ship.

04 · outcomeit goes to prod. that's the only definition of done.

// receipts · last 12 months

^[5]no logos. real outcomes.

2025.11.14migrated stride logistics from a legacy rails monolith → next.js + fly.io · cut infra cost 63%, cut p95 latency 4.2×cloud · web

2025.09.02shipped harbor/fm's triage agent in 19 days · resolved 38% of tier-1 tickets unassisted after 3 weeks of evalai · eval

2025.07.28column·mfg pocket app: expo → tf → production · 0 crashes in first 30 days, app store pass on first submitmobile

2025.05.10northbeam internal console · 9 agency engineers → 1 me · shipped in a quarter, they kept using itweb · ops

2025.02.19rfc + 2-wk audit for a seed-stage fintech · killed a $400k rebuild, kept postgres, shipped the feature in 8 daysaudit

2024.12.03fieldwise ios + android · offline-first, syncs over patchy rural networks · still in production, 0 rewritesmobile

// faq · before you ask

^[6]straight answers.

01 —Is ctlyst really one person?

Yes. Owner-operated. The person you talk to is the person who writes the code. No handoffs, no junior doing the real work.

02 —How fast can you ship?

Weeks to months, depending on scope. Deadline-first — the date is the constraint, everything else flexes around it.

03 —How does pricing work?

Per-project, fixed scope. Retainers optional, hourly when the agreement calls for it. It depends on the deal, and you'll know the terms before anything starts.

04 —Who owns the code?

It depends on the agreement, spelled out in the contract up front. No surprises after the fact.

05 —What do you build?

Web, mobile, cloud, AI, SEO. The right tool for the problem, not the trendy one.

06 —Will you work with my existing team or codebase?

Yes. Drop in, ship, and leave it cleaner than I found it.

07 —What happens after launch?

Project handover, knowledge transfer, and optional support. You're never stranded.

08 —How do we start?

One message. Tell me the problem and the deadline.