Development team, as a service

Your product team, always on.

I'm Joshua. I've built mobile apps for 12 years, for companies like Etsy and Albertsons. Today I build with Claude Code every day, with a small senior team behind me. Your code and accounts stay yours, and you see every change, before and after, every week.

Book a call See how it works
Joshua Bancroft You talk to me, not an account manager
  • Your Slack
  • Your GitHub
  • Your cloud
Pawdcast, week 14 v3.9.0 · Oct 6 – Oct 10
  1. Mon
  2. Tue
  3. Wed
  4. Thu
  5. Fri
  1. New Bark-to-Search Searches per listener 1.2 → 3.4
  2. Fix No more squirrel crash Sessions with a crash 0.4% → 0%
  3. Improved Onboarding: 6 screens to 3 Trial starts baseline → +18%
  4. New Dark mode for night walks Evening listening time 11 min → 17 min
  5. Perf Cold start in under a second Cold start (p50) 2.1s → 0.9s
Each change reviewed by a senior engineer, with a before and after. See the week

An invented example app. One real week of mine: 450 changes, 5 releases.

  • Snackrobat Crash spike in checkout Checkout crash fixed on staging 4m 12s
  • Pawdcast “Can I export my playlists?” Customer question answered 9s
  • Moonmilk Release 3.4.1 tagged 3.4.1 is live on staging 6m
  • Llamalogue New 1★ store review Reply drafted, fix queued 2m 40s
  • Sockpuppet Pay Webhook retries failing Payments flowing again 7m 05s
  • Burrito Cloud Feature request: reorder Reorder button on staging 1h 18m
  • Gravy Train Logistics ANR on route screen Route screen ANR fixed 11m
  • Pawdcast Weekly release cut Weekly update sent 3m
  • Snackrobat “Promo code not working” Customer unblocked 38s
  • Moonmilk Sleep chart looks off Chart fix on staging 14m
  • Llamalogue 4 dependency updates Dependencies up to date 5m
  • Burrito Cloud Trial conversion dipped Paywall test running 22m

Trusted by teams at

What we build

We build with Claude, and we build for it.

We ship production software with Claude Code every day. We know where it is fast, where it needs guard rails, and how to make it reliable on a real codebase: tests it must pass, review before merge, and a before and after picture of every change.

  • Claude agent systems

    Claude Code set up for your team (instructions, skills, hooks, MCP tools, CI), agents that run your routine work on a schedule, and apps with AI inside: reports written by a model, documents read and turned into data.

  • Apps built with AI, made solid

    We pick up an app that you or a builder tool (Lovable, Replit, FlutterFlow, Cursor) got started, make it solid, and take it to the App Store and Google Play.

  • Mobile, native and cross-platform

    Kotlin Multiplatform and Compose, SwiftUI and iOS, Android and Flutter, with Firebase or Supabase behind them. Apps with tens of millions of users included.

Start to finish

How it works, start to finish.

Follow one project from the first call to a shipped app, and every small detail in between.

  1. The idea

    A whole product team, sold like a product.

    One weekly engagement, billed by the hour up to a cap you set. AI does the legwork, a senior engineer reviews every change, and everything runs on your accounts.

    • Weeklybilled by the hour, up to your cap
    • 1named senior engineer
    • 100%of changes reviewed before they ship

    Follow Dana and Pawdcast, an example project

  2. Call booked30 min · no pitch deck
  3. 01 Day 0 · kickoff

    A 30-minute call with a senior engineer.

    Dana shows us Pawdcast, what is broken and what she wants next. We leave with a plan, not a pitch deck.

  4. Call notes in Slack41s after hang-up
  5. 02 Day 1 · Slack

    Your Slack channel goes live.

    Agents join your workspace and reply in seconds. A senior engineer is in every thread and approves the plan.

  6. Access grantedGitHub, Firebase, RevenueCat · yours
  7. 03 Day 2 · team

    Everyone knows who owns what.

    One senior engineer is Dana's point of contact. Specialists cover design, release and cloud; agent squads do the legwork.

  8. Acceptance tests written128 checks · day 9
  9. 04 Weeks 1-4

    The first four weeks, mapped.

    Accounts and agents first, then dev, staging and prod for the whole stack, tests and fixes, and the first release.

  10. Staging link posted6s after the fix merged
  11. 05 Week 2 · Friday

    The first weekly update.

    Every change with a before and after and the number it moved. Dana reads it in two minutes and replies in the thread.

  12. Store review approved4h 12m · first try
  13. 06 Week 4 · release

    Shipped. And it keeps shipping.

    Pawdcast 4.0 is in both stores. From here it is a release every week, with Dana on the call.

Track record

Real numbers and track record

Top Rated Plus and Expert-Vetted on Upwork

  • 450

    Changes shipped in a single week

    on one product, counted and anonymised

  • 5

    Releases that same week

    each with a before and after of every change

  • 12+

    Years building mobile apps

    for Etsy, Bed Bath & Beyond, Albertsons and AT&T

  • 100%

    Changes reviewed by a senior engineer

    AI does the legwork, a senior engineer signs off. Always.

  • Top Rated Pluson Upwork
  • Expert-Vettedon Upwork
  • EtsySeller and Buyer apps
  • Bed Bath & Beyonda whole-app redesign
  • Albertsonsmany brand apps made into one
  • AT&TSmart Home Manager
  • 12+ yearsnative and cross-platform mobile
  • 450changes shipped in a single week

The week's numbers were counted on one product and anonymised. The companies are Joshua's own career. The example products further down the page (Pawdcast, Moonmilk, Snackrobat) are fictional.

Slack, live

Ask in Slack. Get an answer in seconds.

Agents sit in your channels and pick up every message, crash and request. They reproduce, fix, record a before/after clip and open the PR. A senior engineer reviews it, signs off and keeps you in the loop.

Works in your own Slack workspace. You own it; we are invited and removable. Fictional products, people and timings, shown for illustration.

Try it

Ask it something.

Report a bug or ask for a feature on one of our fictional products. The agent answers the way it would in your Slack: what it found, the pull request, a staging link to try, when it ships, and which senior engineer is on it.

  • Repro steps before anyone asks
  • A pull request with before and after
  • A staging link you can tap
  • A real ETA, and a human on it
ask-assistant Demo: scripted replies

Assistant App now

Hi, I'm the AI assistant for Pawdcast, Moonmilk and Snackrobat (all fictional). Ask me about a bug, a feature or a release.

Signals river

Every tool you use. One channel.

Crashes, reviews, payments, deploys and support tickets stream into #signals in your Slack. Agents triage each one in seconds: fix it, hand it to a senior engineer, or save it for the weekly update.

# signalsPawdcast HQ · and friends

live
  1. Crashlytics · Pawdcast 37 crashes grouped into 1 issue · Android 3.8.1 Fixed, Fix PR #483
  2. Stripe · Moonmilk First annual plan from Norway Weekly, Weekly update
  3. Datadog · Snackrobat /orders p95 latency up to 1.2s Engineer, Sam is on it
  4. App Store · Snackrobat New 1★ review: “checkout spins forever” Fixed, Reply + fix #1182
  5. GitHub · Llamalogue 4 dependency updates waiting Fixed, Batched, tests green
  6. PostHog · Pawdcast Trial starts up 18% since new onboarding Weekly, Weekly update
  7. Sentry · Moonmilk TypeError in story player · web Fixed, Fix PR #215
  8. Intercom · Gravy Train “Can I export manifests to CSV?” Engineer, Nadia scoping it
  9. RevenueCat · Pawdcast Renewal webhook retried 3× Fixed, Patched + replayed
  10. Google Play · Pawdcast 3.8.2 approved on Google Play Weekly, Weekly update
  11. Vercel · Moonmilk Preview build failed on main Fixed, Config fixed, green
  12. Linear · Snackrobat Request: tip jar for acrobats Engineer, Planned with Sam

  • 47 this week

    Fixed automatically

    PR opened, engineer-reviewed

  • 9 this week

    Escalated to an engineer

    a human owns it in minutes

  • 26 this week

    Batched into the weekly update

    shown with before/after

Illustrative: fictional products and events. Tool marks are trademarks of their owners, shown as examples of what we connect.

Agents at work

Agents at work, right now.

A crash grouped, a fix tested, a review approved, a build promoted. This is a normal hour on your product: agents doing the work in seconds, a senior engineer signing off on every step.

8 live

Example products and data, for illustration.

Works with your stack

Whatever you run, we already speak it.

Bring the product you already have. We plug into the tools it runs on today, on your accounts, and every one of them reports into your Slack. No rewrite, no migration to "our" stack.

Tools
170+
Verticals
14
Rewrites needed
0

13 tools in Product analytics

Events, funnels, cohorts and dashboards, wired into every feature we ship.

  • PostHog Product analytics
  • Mixpanel Product analytics
  • Amplitude Product analytics
  • Segment Product analytics
  • Heap Product analytics
  • Google Analytics Product analytics
  • BigQuery Product analytics
  • Hotjar Product analytics
  • Plausible Product analytics
  • Matomo Product analytics
  • Umami Product analytics
  • Metabase Product analytics
  • Looker Product analytics

"Works with" means we build on and operate these tools in clients' own accounts. Names and marks belong to their owners and imply no partnership or endorsement.

Ownership

You own everything. We're invited guests.

Your Slack, your GitHub, your cloud. Our engineers and agents join as members you invited, and you can remove every one of them with a single click. Try it.

6 guests connected

Your company Owner: you
Slack workspace moonmilk.slack.com
  • #general
  • #signals
  • #releases

14 members 6 guests

GitHub organization github.com/moonmilk
  • moonmilk-ios
  • moonmilk-web
  • bedtime-api
  • story-engine

100% of the code4 repos

Cloud & services billed to Moonmilk

dev staging prod

Everything is still yours: 1 workspace · 4 repos · 9 services · 3 environments.

Invited guests removable any time

  • Joshua Principal engineer
  • Leo Engineering lead
  • Triage agent AI assistant
  • Build agent AI assistant
  • Monitor agent AI assistant
  • Release agent AI assistant
  • No lock-in Stop any week. There is nothing to migrate or hand back, because nothing ever left your accounts.
  • Your repos Every line of code lives in your GitHub organization from the first commit, in pull requests you can read.
  • Your accounts Cloud, app stores, analytics and every service are opened in your name. We join as invited members.
  • Your data Production data stays in your accounts, under your access rules and your audit logs.
  • Your billing Vendors bill you directly. No resold seats and no middleman on your tooling.
  • Your environments Dev, staging and prod all run in your accounts, so the whole pipeline keeps working without us.

Humans on top

Real senior engineers, on top of every agent.

Every client gets a named senior engineer as their point of contact, plus specialists in mobile, backend, infrastructure, product and QA. They run the agent teams, and nothing ships without them.

  • Joshua Point of contact · Mobile supervises Build, Triage, Updates
  • Nadia Backend supervises Build, Monitor
  • Sam Infra & release supervises Release, Monitor
  • Eric Product & design supervises Updates, Triage
  • Kai QA supervises Release, Build

Joshua reviewed PR #482 and asked the AI for a smaller diffNadia approved the new episodes index the AI proposedSam promoted 3.9.0 (412) to stagingEric rewrote the paywall copy the AI drafted for DanaKai re-ran 43 acceptance checks on a Pixel 8Joshua stepped into #pawdcast-team: "I'll own this one"

  • TriageBugs & questions
  • BuildFeatures & fixes
  • MonitorCrashes & alerts
  • ReleaseStore & staging
  • UpdatesWeekly report

What your engineers do all day

  • Review every pull request

    No agent merges alone. A senior engineer reads each diff, the tests and the before/after media.

    100% of PRs

  • Own architecture

    Data models, module boundaries, dependencies: decided by a human, written down, followed by agents.

    Decision log

  • QA every release

    Real devices, real accounts, the acceptance tree re-run before anything reaches your users.

    Every build

  • Lead the weekly call

    Your point of contact walks you through what shipped, what's next and what needs your call.

    30 min / week

  • Steer the agent teams

    Set priorities, split work, unblock, and step into any Slack thread the moment it needs a person.

    All day

#482 Add Bark-to-Search

Opened by AI · Pawdcast · +418 −37 · 14 files · before/after video

An agent can open a pull request in minutes. It still pauses at a human gate, every time.

  1. PR openedby the AI, 4 min after the request
  2. Automated checks Checks passed · 212 tests
  3. Human gate · architecture Joshua approved · architecture
  4. Human gate · UX Eric signed off · UX · before/after
  5. Human gate · QA Kai verified · QA · 6 devices
  6. MergedOn dev · staging tonight

Three environments

Dev, staging, prod. For the whole stack.

A safe place to try every change before your users see it. Not just the app: your backend, database and analytics run in three copies too, and nothing reaches your users without checks, a human review and your go-ahead.

#482 feat(player): Bark-to-Search · Pawdcast

  1. Branch feat/bark-to-search
    • add voice capture
    • index episodes by bark
    • acceptance: voice search
  2. Gate · CI
  3. Pull request #482 · reviewed by a human
    • Lint & types
    • 212 unit tests
    • Acceptance 43/43
    • Before/after video
  4. Gate · Human review
  5. Dev every merge, minutes later

    dev.pawdcast.app

    • App build 412
    • Backend api dev
    • Database seed data
    • Functions 6 deployed
    • Analytics dev stream

    3.9.0-dev.14

  6. Gate · Acceptance suite
  7. Staging your preview, daily

    staging.pawdcast.app

    • App TestFlight · beta
    • Backend api staging
    • Database prod-shaped copy
    • Functions 6 deployed
    • Analytics staging stream

    3.9.0 (412)

  8. Gate · Your GO
  9. Prod store release · web deploy

    App Store · Google Play · web

    • App phased 10% → 100%
    • Backend api prod
    • Database migrated, backed up
    • Functions 6 deployed
    • Analytics live dashboards

    3.9.0

Release train

Staging every day · production every Thursday · hotfixes any day

W12 3.6.0
W13 3.7.0
W14 3.8.0
W15 3.8.1 · hotfix
W16 3.9.0
W17 3.10.0 · next

The weekly update

Every week, every change, shown.

No vague status reports. Every Friday you get the release: each change with a before and after, a clip of it working, the number it moved, and who checked it. Here is one from a fictional client.

Assistant App to #pawdcast-releases · Fri 09:06

Pawdcast v3.9.0

Podcasts for dogs · Week 14 · Oct 6 – Oct 10

  1. dev Mon 10:12
  2. staging Wed 16:40
  3. prod Fri 09:05
  • 5 changes
  • 2 new
  • 1 fix
  • 1 improved
  • 1 perf
  • 112 acceptance checks passed
  • 0 regressions
  1. New 01 / 05

    Voice search with a live waveform. Paws were never built for keyboards.

    Searches per listener 1.2 3.4 +183%
    • 24 acceptance checks passed
    • Iris · senior engineer sign-off
    pawdcast/app #482 merged
    Before: a text-only search screen with a keyboard and misspelled recent searches.
    After: a glowing mic button with a live waveform that hears “squirrel stories” and shows results.
    Drag to compare
    After, in motion
  2. Fix 02 / 05

    No more squirrel crash

    The player crashed on Android 15 when a squirrel alert arrived mid-episode. Now it keeps playing.

    Sessions with a crash 0.4% 0% fixed
    • 18 acceptance checks passed
    • Kai · senior engineer sign-off
    pawdcast/app #486 merged
    Before: the player behind a “Pawdcast keeps stopping” crash dialog after a squirrel notification.
    After: the squirrel notification slides in and out while the episode keeps playing.
    Drag to compare
    After, in motion
  3. Improved 03 / 05

    Onboarding: 6 screens to 3

    One name, a few vibes, a free trial. Everything else waits until the dog is hooked.

    Trial starts baseline +18%
    • 31 acceptance checks passed
    • Eric · senior engineer sign-off
    pawdcast/app #479 merged
    Before: step 1 of 6, a long form asking for six required details about the dog.
    After: three quick steps, a name, vibes and a free trial button.
    Drag to compare
    After, in motion
  4. New 04 / 05

    Dark mode for night walks

    A low-glow theme that switches on after sunset, with a calm night walk mix up top.

    Evening listening time 11 min 17 min +55%
    • 27 acceptance checks passed
    • Iris · senior engineer sign-off
    pawdcast/app #488 merged
    Before: the bright cream home screen, the same at midnight as at noon.
    After: a dark home screen with a moon, twinkling stars and a night walk mix.
    Drag to compare
    After, in motion
  5. Perf 05 / 05

    Cold start in under a second

    Lazy treats: we load the home feed first and fetch everything else behind it.

    Cold start (p50) 2.1s 0.9s -57%
    • 12 acceptance checks passed
    • Sam · senior engineer sign-off
    pawdcast/app #491 merged
    Before: the orange splash screen with a spinner, “Fetching treats…”, at 2.1 seconds.
    After: the splash pops and the home feed is ready at 0.9 seconds.
    Drag to compare
    After, in motion

Pawdcast is a fictional app made for this page. Real updates link every change to its pull request, its test results and a staging build you can open.

Cadence

Releases you can set a watch by.

Small pull requests merge every day, staging updates several times a day, and production ships on the same day every week. Here are the last 26 weeks of three fictional products.

Releases to production
0
Staging deploys
0
PRs merged
0
Weekly releases on time
0%

Acceptance proof

Every feature has living proof.

A tree of everything your product does, each branch checked and dated. Not a test report once a quarter: a record that updates itself every time we ship.

  1. 01 Written with the feature Each behavior gets its acceptance check in the same pull request that builds it. No proof, no merge.
  2. 02 Re-run before every release Every check runs again on real devices against the release build. Anything a change touched turns amber until it is verified again.
  3. 03 Dated, on the record Who verified it, when, on which device and build, with the screenshot or video. Yours to open any time.
checks on Pawdcast
318
re-run per release
100%
real test devices
11
Pawdcast · Acceptance tree 3.9.0 (412)
Pre-release run · 3.9.0 (412) 41/43

2 checks to re-verify before release

  • Player5 checks · 1 amber
    • Background playback3 checks · 1 amber
      • Squirrel interruptionverified 2h ago·Pixel 8 · Android 15·build 412Pauses for the squirrel alert, resumes at the same barkVerified
      • Lock-screen controlsverified 2h ago·iPhone 15 · iOS 18·build 412Verified
      • Bluetooth collar handofflast verified 3d ago·Galaxy S24 · Android 14·build 405Audio routing changed in #486, re-verify queuedRe-verify
    • Sleep timer2 checks
      • Stops after the episodeverified 5h ago·iPhone 13 mini · iOS 17·build 411Verified
      • Fades out over 30s for nervous pupsverified 5h ago·Pixel 7a · Android 14·build 411Verified
  • Bark-to-Search3 checks · 1 amber
    • Recognizes "woof" as a searchverified 1h ago·iPhone 15 · iOS 18·build 412Verified
    • Waveform while listeningverified 1h ago·Pixel 8 · Android 15·build 412Verified
    • Works offline from the cached indexlast verified 1d ago·iPad Air · iPadOS 18·build 409Index format changed in #482, re-run before releaseRe-verify
  • Paywall & trial2 checks
    • Trial starts from onboarding step 3verified 4h ago·iPhone 15 · iOS 18·build 412Verified
    • Restore purchasesverified 4h ago·Pixel 8 · Android 15·build 412Verified
  • Onboarding2 checks
    • Three screens, skippableverified 6h ago·iPhone SE · iOS 17·build 410Verified
    • Asks for notifications after the first episodeverified 6h ago·Pixel 6 · Android 13·build 410Verified
  • Dark mode for night walks1 checks
    • Follows the system settingverified 9h ago·iPhone 15 · iOS 18·build 409Verified
Verified on this build Code changed since, re-verify queued

A week in the life

A week with us.

Same rhythm every week, so you always know what's coming. Agents never sleep; your engineers keep the rhythm.

  1. Mon 09:00

    Planning from your Slack

    Everything you asked for last week becomes this week's plan. Your point of contact confirms priorities with you in the thread.

    • 7 requests triaged
    • plan posted 09:40
  2. Tue daily

    Releases to staging, every day

    Merged work lands on staging the same day, with a preview link and notes for you to try on your own phone.

    • build 412 on staging
    • preview link sent
  3. Wed 10:00

    The weekly call

    Thirty minutes led by your senior engineer: what shipped, what's next, and the two decisions only you can make.

    • led by Joshua
    • notes in Slack
  4. Thu all day

    QA sweep

    The acceptance tree runs again on real devices against the release build. Anything amber gets fixed or verified before Friday.

    • 43 checks
    • 6 devices
  5. Fri 16:00

    Weekly update, before and after

    Every change with a before/after picture or clip, the numbers that moved, and what goes to your users next.

    • 5 changes
    • cold start 2.1s → 0.9s
  6. Sat 24/7

    Agents on watch

    Crashes, reviews, payments and errors are watched around the clock. Noise is grouped into one issue with a suggested fix.

    • 37 events → 1 issue
    • fix drafted
  7. Sun on call

    An engineer on call

    When something real breaks, a named engineer is paged, acknowledges in minutes and owns it until it's fixed.

    • acked in 4 min
    • hotfix 3.9.1 on staging

Coverage

Someone is always awake.

Senior engineers work across three US time zones. Overnight, AI triages the crash, prepares the fix and hands a ready-to-review pull request to the first engineer who signs on.

Senior engineers Agents Day / night, now
00061218

--:--:--

UTC, live

Agents on watch

Next human handoff in --

  • Los Angeles -- Pacific ·
  • Chicago -- Central ·
  • New York -- Eastern ·
Agents
24/7
Engineers, weekdays
13h
US time zones
3

Onboarding

Live in four weeks.

From the first call to the first release. Agents start answering in your Slack on day one; by week four your whole stack runs in three environments and the first update is in your inbox.

  1. Week 1

    We move in

    Invited into your Slack and GitHub. Agents start answering the same day.

    • Join your Slack workspace and GitHub org
    • Read the codebase end to end
    • Map every service you already use

    You get

    • #product channel with agents replying in seconds
    • Codebase health report
    • Your named senior engineer

  2. Week 2

    Signals on

    Every tool you use starts talking to your Slack: crashes, analytics, deploys, reviews, payments, support.

    • Connect each service as a live signal
    • Group noise into real issues
    • Agents triage the backlog

    You get

    • #signals channel, live
    • First triaged issue list
    • Alerts that reach a human

  3. Week 3

    Three environments

    Dev, staging and prod of the whole stack, with test gates between them. Acceptance trees for what already exists.

    • Stand up dev, staging and prod
    • Add CI gates between them
    • Write acceptance trees for existing features

    You get

    • A staging link you can open
    • An acceptance tree per feature
    • Nothing reaches prod untested

  4. Week 4

    First release

    The first weekly update lands, every change with a before and after, and the first release goes out.

    • First weekly update
    • First release through the train
    • Roadmap call for the next month

    You get

    • Release live in the store or on the web
    • Weekly update with before/after
    • A roadmap you agreed on

Building it yourself?

Building with Claude or Lovable? Good.

We work alongside you: you keep building, we set up the foundations and watch them, week after week. Need less than that? We also coach by the hour while you build.

Book a call

What usually bites at launch

  • Keys and user data left open
  • AI and server costs per user
  • Ad attribution
  • Subscriptions and refunds
  • What breaks at 10,000 users
  • Releasing without breaking production

Pricing

One weekly engagement. You set the limit.

We work on your product every week and bill weekly by the hour, up to a weekly cap you choose. Raise it, lower it or pause it any week. No fixed quote that the real work outgrows.

  • Billed weekly

    by the hour, for the work actually done

  • Your weekly cap

    we never go over it without asking

  • Raise, lower or pause

    any week, as your plans change

How a week with us works

Launch is the start. Every week ships.

An app needs care every week: fixes, store updates, new features and growth tests. We stay on it with you, at the pace you set.

  • One call a week: we show what was built and agree the next week's work with you.
  • You can try every change before it goes out (TestFlight, Play test track, staging link).
  • A short written report every week, with a picture of every change, before and after.
  • Everything stays in your accounts: your GitHub, your Slack, your cloud.
Book a call

We agree the hourly rate and your weekly cap on the call, before any work starts.

The team

Meet the engineers who review every change.

Real people you can talk to. Every client has a named senior engineer and a few specialists who review every pull request, own the architecture, run the weekly call and keep the AI honest.

Portrait of Joshua Bancroft

Joshua Bancroft

Founder · Principal Engineer

  • Mobile architecture
  • Kotlin Multiplatform
  • UI/UX design

Senior engineer and UI/UX designer with 12 years in mobile, from startups to Etsy, Workday, Nike SNKRS and Axon. Founded Elevation Mobile.

Portrait of Eric Nabeth

Eric Nabeth

UI/UX Designer

  • UI/UX design
  • App features end to end
  • First-run experience

Theatrically trained UI/UX designer crafting intuitive app features from the user's perspective.

FAQ

Straight answers.

Ownership, security, coverage and what happens if you leave. Anything else, ask us on a call.

Book a call

  • Me, Joshua. You talk to me, not an account manager. I review every change, run the weekly call and bring in specialists for design, backend, QA and release when your product needs them.

  • Yes. We pick up apps that a founder or a builder tool got started, make them solid and take them to the App Store and Google Play. You can keep building alongside us.

  • You do. Everything lives in your GitHub organisation from the first commit, and every service runs on accounts you own. We are invited in as members, never owners.

  • It answers questions, triages signals, writes code, opens pull requests and runs tests around the clock. It cannot merge to production, change access, spend money or talk to your customers. A senior engineer reviews every pull request and approves every release.

  • Least privilege on your own accounts: scoped roles, service accounts where a tool supports them, secrets in your vault, never in code. Every access is listed for you and can be revoked in one click.

  • Nothing breaks. You already own the code, the environments, the Slack history and every account. Remove us, and your team or another one picks up from a clean repo with tests and docs.

  • Native iOS and Android, Kotlin Multiplatform, Flutter, React Native, the web (React, Next.js, Astro and friends) and the usual backends: Firebase, Supabase, AWS, Google Cloud, Azure, Rails, Node and Postgres. If it is in your repo, we can work in it.

  • AI replies in your Slack in seconds, at any hour. A senior engineer follows up within your working day, and production issues come first.

  • AI watches your signals around the clock. Engineers cover North American and European hours, and production issues come first.

  • Billed weekly by the hour, up to a cap you set. Raise it, lower it or pause it any week. No fixed quote that the real work outgrows.

  • Yes, happily, before the first call if you like. All work product and IP is yours, in writing.

  • Yes. They use the same repo, the same Slack and the same pull requests. The AI answers their questions too, and our engineers review their code like anyone else's if you want.

Agents on shift now · --:-- your time

Your product team, starting Monday.

Thirty minutes with a senior engineer. Bring an idea, a half-built app or a product with users; leave with a plan for your first week.

Book a call
  • You own every account
  • Senior engineer on every PR
  • Billed weekly, up to your cap

Keyboard shortcuts

⌘ K
Command menu
/
Command menu
?
This list
T
Toggle theme
G thenH
Go to Overview
G thenL
Go to Slack, live
G thenS
Go to Any stack
G thenO
Go to You own everything
G thenW
Go to The weekly update
G thenP
Go to Pricing
G thenT
Go to Team
G thenF
Go to FAQ
G thenB
Book a call
Esc
Close

↑ ↑ ↓ ↓ ← → ← → B A · you know what to do
Your product team, always on Book a call