Complete one existing user task in a runnable React/TypeScript web app. The fixed fee is USD799, after we confirm fit and you approve the written scope.
What you receive
- One agreed workflow across up to three existing screens, using existing tables, API contracts and authorization.
- A reviewable code change in your repository or agreed handoff format.
- Five written acceptance cases and evidence of their results.
- One named neighboring behavior checked for regression.
- A plain-language change summary, run instructions, limits and rollback notes.
- One in-scope adjustment and seven days of scoped defect support.
A sample definition of done
An already signed-in user creates a service request and sees its submitted status when reopening it. The screens and permissions already exist. These are illustrative cases; yours are agreed before the invoice.
- Valid: expected values produce exactly one request and the correct success state.
- Invalid: missing required input produces a useful message and no record.
- Persistent: reopening and refreshing the real route retains the values and status.
- Repeated: a repeat action does not accidentally duplicate the submission under agreed conditions.
- Recoverable: a controlled failure preserves safe input and permits a deliberate retry.
The nearby regression might be opening an existing request without changing it. Five cases do not certify your entire app.
Fit before payment
We need an owner-authorized, runnable repository, reproduction steps, synthetic test data and a safe environment. An app URL helps us understand the task; it is not permission to probe your systems. We agree the actor, routes, dependencies, acceptance cases and start date in writing.
What needs another scope
New authentication or billing systems, auth-email delivery, search indexing, security or RLS fixes, migrations, new apps, native mobile releases and whole-app rescues are outside this offer. So are third-party outages and incidents requiring emergency coverage.
If a hidden dependency makes the accepted task infeasible, we explain it. We do not silently replace your workflow with a broader project.
Timing and ownership
We confirm a realistic start and target handoff date after fit review. One workflow delivery is active at a time. Your accounts and code stay yours. Production release requires your separate approval; preview acceptance does not automatically authorize a live deployment.
Revision, support and remedy
One in-scope adjustment is included, with a 45-minute working allowance. New actors, screens or outcomes need a separate agreement. After handoff, seven calendar days cover defects introduced by our change against the agreed cases, with up to 60 minutes of correction plus triage. Business-day replies; no emergency SLA.
Buyer changes, provider outages and unrelated defects are outside that support. If we cannot deliver the agreed cases, we offer a refund of the implementation fee and a clear findings/rollback handoff. If an in-scope support issue cannot be resolved within its boundary, we agree a remedy rather than leave an unexplained stop.