Work Credits for marketplace development
Pre-purchase senior engineering time for an approved backlog. Use it for scoped fixes, improvements, and investigation while keeping estimates, approvals, time logs, and review in one client dashboard.
Base rate
$100/hour
First purchase
10 hours
Acknowledgement target
One business day
Capacity is not an emergency-support contract
Request triage happens through the client dashboard. Start timing is confirmed after review. Emergency or 24/7 coverage is included only when a separate support agreement says so.
Choose Your Hours
$100/hour • Minimum 10 hours
Add 15 more hours to save 5%
Non-expiring hours; governing terms are shown before payment
FIT BEFORE PURCHASE
A Bounded Way to Move the Backlog
Work Credits are useful when the work is incremental and the client can approve priorities. Full builds and open-ended risk need a different engagement.
Best for
- Approved bug fixes and maintenance on an existing platform
- Small features, integrations, and workflow improvements
- Performance, analytics, security, and UX backlog items
- Investigation where the first task is to find the responsible fix
Not designed for
- A complete marketplace or directory build
- Undefined production emergencies or 24/7 coverage
- Work that needs research workshops before it can be estimated
- A request with no accountable owner or safe access path
VISIBLE CONTROL
How Each Request Moves
The hours are flexible. The decision process is not.
1. Triage
Submit the request in the client dashboard. We review scope, urgency, access, and dependencies.
2. Estimate
We confirm the expected hours and earliest available start. Larger or unclear work is broken into a bounded investigation first.
3. Approve
You approve the request before we consume the estimated capacity. If the estimate changes, we pause and ask before continuing.
4. Deliver and review
We log approved time, attach evidence, and return the work for review through the dashboard.
CLEAR TERMS
Questions Before You Purchase
If the responsible path is smaller than a credit package, we will say so.
Why does the first purchase start at 10 hours?
Secure onboarding, codebase review, access checks, backlog triage, and initial delivery context create fixed setup work. Existing clients can top up from five hours. If your task is likely smaller, contact us before purchasing and we will recommend the smaller responsible path.
How quickly will you respond or start?
Our standard acknowledgement target is one business day. Scheduling follows after we review the scope, urgency, access, and available capacity.
What happens when an estimate changes?
We stop before consuming unapproved capacity, explain what changed, and give you the choice to continue, reduce scope, or pause. The dashboard keeps the estimate, decision, and time record together.
Are bug fixes unlimited?
No. Work Credits are finite purchased hours. You can use them for approved fixes, features, or investigation, and the actual approved time is deducted from your balance.
Do Work Credits expire?
No. Purchased Work Credit hours do not expire. They remain available until used on approved requests or resolved under the refund terms that applied at purchase.
Can I use Work Credits for a full build?
Work Credits are best for incremental backlog work. Complete builds use a scoped proposal, milestones, acceptance criteria, and project terms. If responsible pricing needs research first, we propose a separate paid Discovery Phase.
Start with the smallest responsible commitment
Purchase capacity when you have an incremental backlog, or send the request first if you are unsure whether Work Credits fit.