Intake
Collect the real inputs
Start with the current state.
- Gather the app, site, store, CMS, hosting, files, exports, screenshots, or logs that matter.
- Write down what is broken, overdue, or blocked plus any deadline.
Process
A clear method for moving digital work from intake to finished result.
From one broken step to a multi-phase build, the work stays clear from review through final notes.
- Apps, websites, stores, code, AI workflows, data, dashboards, and files follow the same written review path.
- Implementation, testing, and final notes stay explicit whether the work is a fix, a build slice, or a recurring lane.
- AI-assisted workflows are scoped, tested, and handed off like other digital work.
- Hosting, domain, email, deployment, and access changes stay staged when live systems are involved.
Operating method
Nine checkpoints from intake to clear final notes.
Some work is a focused fix; some becomes a build phase or recurring lane. The same control points apply when app, site, hosting, data, documentation, AI workflow, or code work touches something important.
Diagnostic review
Find the likely cause and constraints
Separate diagnosis from execution.
- Review the available material before proposing the fix path.
- Flag missing access, context, or risk early.
Scope and risk check
Write the boundaries
Write the boundaries before work starts.
- Confirm what is included, excluded, and dependent on third parties.
- For AI workflows, confirm source material, expected output, review rules, escalation rules, testing, and handoff.
- Mark anything that can affect live systems or needs approval.
Fixed-scope plan
Set the work package
Set the work package before execution.
- Confirm the output, files, notes, timing, tests, and review point.
- Decide whether the task is a direct fix, a build phase, a workflow change, or staged for before/after review.
Approval and payment
Confirm before work starts
Confirm scope, access, and payment before execution.
- First-time fixed work is normally paid upfront.
- Larger work can use milestones; CAD is the default and USD is available on request.
Execution
Build, fix, automate, or stage the work
Complete the approved task cleanly.
- Use the right implementation path across React, JavaScript, TypeScript, HTML/CSS, PHP, templates, forms, files, LLM-powered tools, or platform-native changes.
- Keep risky moves visible and quote new scope separately.
Checks
Check against the agreed outcome
Check against the agreed finish line.
- Run the agreed checks against links, deploy behavior, data outputs, files, scripts, dashboards, forms, AI-assisted workflows, or workflows.
- For AI outputs, review against source material and business rules; document escalation rules and limits so the workflow does not invent facts or make unsupported promises.
- Confirm the result matches the approved outcome before handoff.
Handoff
Leave a usable record
Leave a usable record for the owner.
- Summarize what changed, what was checked, and which files or settings were touched.
- Include before/after notes, open items, known risks, and next-step recommendations.
Recurring execution or follow-up
Keep recurring work visible
Move recurring work into the right queue.
- Add suitable recurring tasks to a monthly lane.
- Quote the next fixed-scope phase separately when it is needed.
Scope control
The work stays controlled by design.
Control stays readable when it is written down before the work grows from a quick fix into a larger phase.
- Assumptions, exclusions, and access needs are documented early.
- Production-impacting changes wait for approval.
- New scope is quoted separately instead of blurring the original task.
Before execution
Assumptions are written before execution.
- Dependencies and access needs are called out early.
- Exclusions and open risks stay attached to the task.
Before live changes
Production changes wait for sign-off.
- Website, template, plugin, domain, email, hosting, AI workflow, or data edits are flagged before they land.
- Staging or before/after review is used when that is safer.
Quoted separately
New asks do not blur the current task.
- New requests are captured and quoted separately.
- Minor corrections inside accepted scope stay inside the original task.
Access and security
Access is requested after the work path is clear.
Access should stay limited and reversible.
- Most tasks can start from URLs, screenshots, exports, files, logs, or notes.
- Platform access should be limited to the approved task and removed after completion.
- Please do not send passwords or secret keys by email.
- Use temporary users, collaborator invites, or one-time secret links when access cannot be avoided.
Why this helps
Least-privilege access keeps the work moving.
- Customer accounts stay protected while the task keeps progressing.
- The approved work gets enough access without exposing more than it needs.
Backup and rollback mindset
Changes should have a way back or a reason they are staged.
Not every task needs a complex rollback plan, but risky work still needs a way back.
- Live website, app, domain, email, hosting, deployment, data, AI-assisted workflow, and recurring workflow changes need review.
- Use staging, drafts, branches, prepared patches, or before/after review when practical.
- Keep rollback notes and verification steps close to the work.
Typical controls
- Confirm current owner and access path.
- Check backups, exports, or previous versions before risky changes.
- Use staging, drafts, branches, prepared patches, or before/after review when available.
- Document rollback notes and verification steps.
- Hold production-impacting changes for approval.
No open-ended unpaid work
Early discussion stays focused on fit, scope, timing, risk, and access.
- Deep diagnostic review and implementation live inside an approved paid scope.
- Execution, testing, and the final summary are not expanded into unpaid work.
Checks and final notes
The record should be usable after the task closes.
- Summaries cover changes made, links or files touched, and checks performed.
- Screenshots, open risks, access notes, and carry-forward items stay visible when useful.
Ready to scope digital work?
Start with the current state, the desired outcome, and any deadline.
The first useful answer is usually a tighter scope, the right phase, and the access questions needed to proceed. Most work can be scoped, completed, reviewed, invoiced, and wrapped up in one written thread.