home

Senior web development on a monthly subscription

Andrew Rymer, senior engineer, 10 years building web applications

You get 10 years of architecture, security and full-stack decisions, and my tooling handles the repetitive work so more ships each month. Every request comes back as one pull request I've already reviewed, tested, and approved.

How it works - From first conversation to reviewed pull request

I make the decisions on architecture, security and scope. AI coding tools do the repetitive build work, which is why more ships each month than one engineer could write by hand.

  1. step_01

    Start with a Project Assessment

    Tell me what you're after: fixing problems, getting an MVP production ready, moving to a new framework, or adding or overhauling features. After a 60-minute kickoff call, I review your code or plan and deliver a written, prioritized plan and a proposed first month of requests within 5 business days. Then I walk you through it on a 60-minute call.
  2. step_02

    Subscribe

    Pick Standard or Pro. The $1,500 comes off your first month, and you can cancel anytime.
  3. step_03

    Send requests

    Add requests to a backlog you control and reorder it whenever priorities change. Each request is one shippable change, and bigger asks are split into several.
  4. step_04

    I plan it, my tools build it

    I turn each request into a ticket with clear acceptance criteria. My AI coding tools write the first version on a separate branch, and a review tool checks it.
  5. step_05

    Get a reviewed PR

    I read the diff, test it, and send it back for fixes until I'd be happy to own it. Every request arrives as one pull request I've already reviewed, tested, and approved, ready for you to merge.

Pricing - Two plans, one way in

Every subscription starts with a Project Assessment, and its $1,500 fee is credited in full to your first month.

Standard

plan_01

$3,995 / month

One active request at a time, with turnaround in 2 to 3 business days.

Pro

plan_02

$6,495 / month

Two requests at once with priority, and turnaround in 1 to 2 business days. Limited to one client.
View pricing

FAQ - Questions founders and small teams ask

Straight answers on ownership, access, billing and how requests work.

  1. q_01

    Who owns the code you write?

    You own all the code and work product we deliver once each invoice is paid. The AI tools and workflow I use to build it stay with Arc Digital, but nothing in your code depends on them. Any developer can run, change or take over your code without me or my tools.
  2. q_02

    How do you get access to our repo?

    You add Arc Digital to only the repos you name. On GitHub that's an outside collaborator with Read access, and GitLab Reporter, Bitbucket Read and Azure DevOps Reader work too. The Project Assessment is read-only. For a subscription, you choose Write access with branch protection on your default branch, so every change comes as a pull request and nothing is pushed directly, or a fork, where we open pull requests from our own fork. Either side can remove access when the work ends, and we confirm it in writing the same day. We never ask for production credentials or environment values. If config is needed, you share it through a one-time secret link or your own secrets manager.
  3. q_03

    Will you sign an NDA?

    Yes. We're happy to sign your NDA, or we can use our own mutual NDA. Either way, it's signed before we see any code. Your code and data stay confidential, and we only access what you grant.
  4. q_04

    What AI tools do you use?

    I'm Andrew Rymer, a senior engineer with 10 years building web applications, and I plan each request and make the architecture and security calls. For coding and code review I use tools from xAI (Grok), Anthropic and Greptile, plus Warp's cloud agents now and then. They handle the repetitive work, which is why more ships each month. I review, test and approve every pull request before it reaches you.
  5. q_05

    What is the Project Assessment?

    The Project Assessment is a fixed $1,500 first step. Andrew reviews your code or plan, then delivers a written, prioritized plan for your goal, such as fixing problems, getting an MVP production ready, moving to a new framework, or adding or overhauling features. It arrives within 5 business days of a 60-minute kickoff call, and Andrew walks you through it on a separate 60-minute call at the end. The full fee is credited to your first month.
  6. q_06

    How does billing work?

    Every engagement starts with a one-time $1,500 Project Assessment. After that, you subscribe to Standard or Pro and are billed monthly through Stripe. The Project Assessment fee is credited in full to your first month, so month one is $2,495 on Standard or $4,995 on Pro. There are no hourly rates or metered charges.
  7. q_07

    Is AI usage really included?

    Yes. I'm the one using the AI tools, on your requests, and that usage is part of your monthly price. You won't see AI charges on your invoice. If a month runs unusually heavy, I'll let you know, but you won't be billed extra.
  8. q_08

    Can I cancel or pause?

    Yes. You can cancel anytime in the Stripe customer portal, and your plan stays active until the end of the period you've paid for. Requests you send before the cycle ends still get finished. Canceling is also how you pause, since there is no separate pause option.
  9. q_09

    What if I come back later?

    If you return within 3 months of canceling, you can resubscribe right away with no new Project Assessment. If it's been longer than 3 months, a new Project Assessment comes first, because your code and goals have usually moved on.
  10. q_10

    Can I switch between Standard and Pro?

    Yes. You can switch plans in the Stripe customer portal, and the change is prorated right away. Pro is limited to one client, so it may be full when you ask.
  11. q_11

    How fast is turnaround?

    Standard requests are delivered in 2 to 3 business days. Pro requests are delivered in 1 to 2 business days and get priority in the queue. Turnaround is per request, so a bigger ask that is split into several requests takes several of those cycles.
  12. q_12

    What counts as a request?

    A request is one shippable change that arrives as one reviewed pull request. A bug fix, a new form or a small feature are typical examples. Bigger asks are split into several requests, and anything waiting sits in an unlimited backlog you can reorder.

next

Start with a clear plan

Whether you're fixing problems, getting an MVP production ready, changing frameworks or adding features, the Project Assessment gives you a written, prioritized plan and a proposed first month of requests within 5 business days of a 60-minute kickoff call, followed by a 60-minute walkthrough.

Book a Project Assessment