Launch is the beginning, not the finish line

Yes. We onboard into an existing codebase the same way we would our own — a short review up front to understand the architecture, then support starts on your plan’s timeline.

Any defect in a change we delivered, fixed for as long as you need it — once you’ve completed 6 consecutive months on any plan, or just 2 consecutive months on Priority. It does not cover breakage caused by a new OS release, a third-party API or SDK change, or edits made outside Applefy after we delivered the work.

A small improvement is a tweak to something that already exists — a copy change, a UI adjustment, a minor workflow fix. A new feature, a redesign, or anything that needs its own scoping and design work is a project, not maintenance, and we’ll quote it separately rather than squeeze it into the plan.

Yes, month to month. Most clients start on Care or Growth and move up as the product grows.

That’s fine — plans are month to month with no minimum term. The Lifetime Fix Guarantee simply starts once you reach 6 consecutive months (2 on Priority).

The per-plan response time (2 business days on Care, 24 hours on Growth, same-day on Priority) is for routine requests. A genuine critical issue — an outage, data at risk, a security exposure — gets fixed within 24 hours regardless of plan; it never waits behind the routine queue.

Not exactly, though Priority includes Fractional CTO-level guidance as part of the plan — architecture direction, hiring input, and technical decisions, alongside the hands-on maintenance work. On Care and Growth, Fractional CTO remains a separate, complementary engagement rather than something bundled in.

Not directly — this plan keeps what you have running and polished, it isn’t a channel for new feature development. Bring us the idea and we’ll scope it as its own project, so it gets the design and planning a real feature needs instead of being squeezed in alongside bug fixes.