Scope before code
Deliverables, acceptance criteria, and exclusions are agreed first.
Fixed-scope software delivery
Blocked by a software issue?I turn it into a shippable result.
Bug fixes, test automation, AI API integrations, Docker/CI/CD support, and multilingual technical SEO for small SaaS teams, startups, and open-source projects. You receive a written scope and quote before implementation begins.
Delivery is evidenced by a focused PR, a working build, test results, and concise handover notes.
Working principles
A small engagement should still leave a clean trail.
Verifiable delivery
Work is delivered through focused code changes, tests, build results, and handover notes.
Minimum necessary change
The goal is to remove the blocker, not turn every task into a rewrite.
Fixed-scope services
Buy a result, not an open-ended development promise.
Each sprint starts with a bounded problem and ends with evidence you can review. Final scope and price are confirmed in writing.
01
Bug Fix Sprint
Diagnosis, implementation, tests, and a focused PR for one reproducible issue.
Ask about this sprintTypical delivery
- Root-cause note and bounded implementation
- Relevant tests or reproducible verification
- Focused PR and handover notes
Not included: Unlimited investigation or architecture rewrite
02
Test & Release Sprint
Create an automated baseline for a critical journey or remove a build, CI, or release blocker.
Ask about this sprintTypical delivery
- One critical automated path
- Repeatable build or release command
- Failure notes and remaining risks
Not included: Full test-suite coverage
03
AI Integration Sprint
Connect one model or AI API to an existing product through a minimal, observable working flow.
Ask about this sprintTypical delivery
- One end-to-end AI-assisted workflow
- Structured output and error handling
- Basic limits and cost safeguards
Not included: Model fees and complex production governance
04
Multilingual SEO & i18n
Implement localized routes, metadata, canonicals, sitemaps, structured data, and a maintainable content flow.
Ask about this sprintTypical delivery
- Localized route and metadata baseline
- Canonical, hreflang, sitemap, and schema
- Maintainable translation handover
Not included: Large-scale human translation or content operations
Selected work
Evidence from systems already in motion.
Anonymized project notes showing how production risks were mapped, repaired, and handed over.
01 / Incident recovery
Legacy WordPress Recovery
- Context
- A production site was failing during a runtime upgrade, with intermittent gateway errors and no dependable rollback path.
- Contribution
- Reproduced the failure in staging, isolated incompatible paths, and built a controlled recovery and release sequence.
- Result
- A stable release path with clearer health checks, backups, rollback ownership, and operational handover.
WordPressPHPNginxMySQL
Read the case study 
02 / Payments and back office
China Payment Gateway Integration
- Context
- Gateway callbacks, local order states, and back-office review steps had to remain consistent under real transaction traffic.
- Contribution
- Mapped checkout and callback verification, implemented traceable failure paths, and prepared reconciliation views for operations.
- Result
- Payments became easier to verify, reconcile, and support across customer and operations workflows.
DrupalPayment APIsPHPRedis
Read the case study 
03 / CRM automation
SuiteCRM + WordPress Automation
- Context
- Leads arrived through several forms and needed consistent validation, ownership, follow-up, and client notification.
- Contribution
- Mapped source fields, added duplicate handling and assignment rules, and created a QA handover for production.
- Result
- Less manual copying and clearer visibility into lead status, ownership, and exceptions.
SuiteCRMWordPressREST APIsEmail automation
Read the case study Process
Four steps from blocker to handover.
- 01
Share the issue
Expected behavior, actual behavior, reproduction steps, and any repo or demo you are authorized to share.
- 02
Confirm the scope
Receive written deliverables, acceptance criteria, exclusions, and a quote.
- 03
Implement and verify
Changes are made in a focused branch or PR and checked against the agreed criteria.
- 04
Deliver and hand over
Receive code, verification results, merge or deployment notes, and known follow-ups.
Ways to work together
Choose the smallest useful commitment.
Paid diagnosis
For problems whose root cause is unclear and cannot yet be quoted responsibly.
Fixed-scope sprint
For one bounded outcome with a clear acceptance path.
Monthly maintenance
For recurring fixes, release support, and gradual technical-debt cleanup.
No unlimited revisions, 24/7 on-call promise, or guaranteed outcome before the system is inspected.
FAQ
Boundaries are part of reliable delivery.
01Can you fix an issue without learning the entire codebase first?
A paid diagnosis can come first. Fixed-price implementation begins only when the reproduction path, relevant modules, and acceptance criteria are clear enough.
02Do you accept urgent work?
You can state the urgency, but acceptance depends on current availability, access conditions, and risk. No deadline is promised before the scope is reviewed.
03Will you sign an NDA?
An NDA can be reviewed when the project requires it. Code, business data, and screenshots are not published without authorization, with or without an NDA.
04How does payment work?
The payment method, milestones, acceptance window, and any refund conditions are confirmed in writing before work begins. Small bounded tasks may require prepayment or platform escrow.
05Is support included after delivery?
Each scope includes a written acceptance window. New features and issues outside the agreed scope are quoted separately.
06Do you use AI coding tools?
Tools may assist research, testing, and implementation, but delivery is judged by working code, test results, and human review. Client secrets are not submitted to unauthorized third-party services.
Start with the blocker
Describe the issue before we discuss implementation.
Share only information and links you are authorized to disclose. I will first confirm whether the work fits a bounded sprint.
Prefer email?ruo@deng.in