devsan

Services

A product, used. Not just a product, shipped.

What you actually get when you hire me: a product, used.

Most freelance pitches sell strategy, discovery, or “alignment.” I sell a deployed product. I take the problem from first conversation through data model, build, deploy, and the parts most engineers skip — SEO, security headers, accessibility, monitoring, a launch plan, and outreach to the first real users.

I lean hard on AI tooling to ship at small-team speed for single-engineer cost: parallel agents, the right model per task, prompt caching.

What I build

Four ways to work together.

Each engagement is single-engineer ownership, end-to-end. Pick the one that fits — or describe the problem and I'll tell you which it is.

01 · Web products

Production web products

MVPs, customer-facing platforms, and internal tools — Rails or Next.js, end-to-end. I own the data model, the API, the UI, the deploy, and the moving parts most freelancers ignore.

Typical deliverables

  • Data model, API, and UI built around the real workflow
  • Auth, roles, billing — wired up cleanly, not glued on
  • Deploy on AWS or a managed host with CI/CD and rollback

02 · AI agents

AI agents and automation

Agentic features, MCP servers, prompt-cached LLM pipelines. Python by default; Rails when the agent has to live inside a Rails app. Built for observable cost and predictable output, not vibes.

Typical deliverables

  • Typed tool surface (MCP or function-calling) over your real data
  • Per-call metering, cost attribution, and a fallback chain
  • Evals + a transparent prompt cache strategy

03 · DevOps

DevOps-backed scalable systems

If the bottleneck is infra, I'll fix that too. Docker, AWS, CI/CD, environments, observability. Same engineer who built the product also owns the deploy — no handoff tax.

Typical deliverables

  • Containerized build, repeatable across environments
  • CI/CD with preview deploys and a real rollback path
  • Logs, metrics, and alerts wired to a channel you read

04 · IoT

IoT and embedded prototypes

ESP32 / ESP32-S3 builds with BLE, OLED, sensors, and servos. Useful for product validation, in-store demos, or hardware companions for a software product you already ship.

Typical deliverables

  • Firmware tuned around a few rock-solid hardware actions
  • BLE / Wi-Fi handoff to your app or desktop host
  • Spec-driven state machine, not ad-hoc loops

Beyond the deploy

The unglamorous work that decides whether a product gets used.

Every engagement includes these. Not as upsells — as the baseline. A product that ships without them is a product nobody finds.

  • SEO baseline

    Meta tags, OG, structured data, sitemap, indexing checks. Submitted to Search Console before you ask.

  • Security headers

    CSP, HSTS, frame-options, referrer policy. Auth surfaces audited for the obvious holes.

  • Accessibility pass

    Keyboard nav, focus states, labels on every input, color contrast at AA. Not theatre.

  • Observability

    Real logs, real metrics, real alerts — in a channel you actually read. Not a dashboard graveyard.

  • Launch plan

    A short doc covering positioning, the first thing users see, and the first week of iteration.

  • First-user outreach

    I help find and talk to the first real users. Not influencer fluff — actual product feedback loops.

Got a problem in mind? Send me a paragraph.

I read every message and reply within 24h. If it's a fit, you'll have an honest scope back in a day — what I'd build, what I'd skip, and what it costs.