Offers — Follow or Bounce

What I build

Follow or Bounce is a one-person studio. I design and build AI and agentic systems, add intelligence to existing products, and ship fast static sites and interactive pieces. Small scope, direct contact, working software.

Custom agents & automations

2–6 weeks, fixed scope

A task-specific agent or automated workflow that does one job well — tool calls, retrieval, structured output, human check-points.

  • Scoping: the task, the tools, the failure modes, the eval
  • Agent / pipeline implementation with tests
  • Prompt + tool design, guardrails, cost controls
  • Deployment (your infra or a small hosted service) and a runbook

AI integration for existing products

3–8 weeks

Add LLM features to an app or site you already run — assistants, semantic search / RAG, structured extraction, classification, summarization.

  • Architecture: model and stack choice, data flow, privacy
  • Retrieval + indexing pipeline where relevant
  • Feature implementation behind a clean interface
  • Evals, logging, and a plan for iterating after launch

Technical advisory & audits

Hourly or monthly retainer

A second set of hands on the hard calls — architecture review, model and vendor selection, prompt and eval strategy, cost and latency work.

  • Codebase / architecture review with written findings
  • Model + cost analysis, correlation of quality vs. spend
  • Eval design so quality is measured, not guessed
  • On-call review during a build (retainer)

Static sites & interactive builds

1–4 weeks

Fast, hand-built sites with no CMS to rot — one-page sites for small operators, and long-scroll editorial / landing pieces in the style of the Writing section.

  • Design and build in a clean, documented system
  • Deploy to static hosting (GitHub Pages / Netlify) — near-zero running cost
  • Contact form, metadata, sitemap, performance pass
  • Handover: the repo is yours, plainly documented
  1. 1

    Brief

    A short call or a written brief. What the thing needs to do, for whom, by when. I'll say if I'm the wrong fit.

  2. 2

    Direction

    A fixed proposal — scope, price, timeline, and what I need from you. Half up front to start.

  3. 3

    Build

    Working software in your hands early and often. One clear channel, weekly checkpoints, no status theatre.

  4. 4

    Handover

    The repo, the runbook, the evals. A short window of support to shake out issues. Balance due on delivery.

How do you price?
Fixed price for fixed scope, wherever the scope can be pinned down. Retainer or hourly for advisory and open-ended work. You get the number before anything starts.
Payment terms?
50% to book the slot, 50% on delivery. Retainers are billed monthly in advance.
Who owns the work?
You do — code, prompts, and assets transfer on final payment. I keep the right to describe the work and show non-confidential parts.
What's the stack?
Whatever fits: typically Python or TypeScript, the current strong models, and boring, inspectable infrastructure. I'll justify the choice in the proposal.
Do you sign NDAs?
Yes, a straightforward mutual NDA is fine before sharing anything sensitive.

Start a project

Tell me what you're building