New Features From the Team That Knows Your Code.
Growth and Scale plans include monthly feature hours. Describe what you want in plain English — we scope it, estimate the hours, and build once you approve. No surprises.
Small improvements built by engineers who know the codebase.
Feature hours are for additions that extend what already works — not rebuilds or large new directions.
Because we already maintain your codebase, we can build these additions faster and more safely than any outside developer who would need weeks just to understand your system.
New pages or sections added to your existing app
Form updates — new fields, validation logic, submission handling
Workflow changes and simple automations
API integrations with third-party services (standard scope)
Dashboard updates — new charts, filters, data views
UI improvements and small-scope redesigns
Email templates and transactional notifications
User role and permission changes
Plain English in. Working feature out.
No technical spec required. We translate your description into a scope document, estimate hours, and wait for your approval before building.
Describe it in plain English
Tell us what you want. No technical spec required. We understand your codebase — you just need to explain what you want it to do.
We scope and estimate hours
Within 24 hours we investigate the codebase, check for impact on existing functionality, and send you a written scope with a time estimate.
You approve before we start
Nothing gets built without your sign-off on the scope and hours. If the estimate is higher than expected, we discuss alternatives.
We build in a feature branch
Development happens in isolation. We follow your existing patterns and coding conventions so new code reads like it belongs.
Review on staging
Deployed to staging for your review before anything touches production. Iterate until it matches your expectations.
Deploy to production
Coordinated production deployment at a time that minimises disruption. Migration-safe if schema changes are involved.
Included hours per plan.
Unused hours do not roll over. This is intentional. Monthly feature work keeps your product improving on a steady cadence rather than accumulating a backlog that gets built all at once and introduces risk.
The kinds of things feature hours get done.
Actual requests from clients, with the hour estimates we provided.
"Add a CSV export to the admin dashboard"
Query builder for current filter state, CSV generation on the backend, download trigger on the frontend.
"Send a welcome email when a new user signs up"
Email template, transactional send via existing provider, trigger on registration event.
"Add a 'pending' status to orders"
Schema migration for the new status, UI state updates, admin filter update, customer-facing status display.
"Create a simple analytics page showing signups per day"
Date-grouped query, chart component, date range filter, basic loading and empty states.