Execution first
Clear deliverable, acceptance check and handoff note instead of vague consulting or open-ended support.
Remote technical execution / GMT-3
I turn messy technical asks into a reviewable first pass: the fix, workflow, dashboard, integration, QA packet or launch handoff, plus the checks a buyer can inspect before the scope grows.
The strongest jobs are concrete: one broken WordPress flow, one n8n scenario, one supplied Figma-to-WordPress build, one AppSheet/Sheets ops system, one API/webhook path, one React Native/Expo MVP pass, one dashboard problem, one import, one Base44/no-code app pass, or one AI workflow that needs guardrails, logs and validation.
Clear deliverable, acceptance check and handoff note instead of vague consulting or open-ended support.
Credentials, billing, platform approvals, Meta/WhatsApp limits, payment flows and production access are handled explicitly.
Proof assets are now short PDFs or exact-fit demos only when they clarify the job; generic links are avoided.
Reports, repos and proof routes show commands, screenshots, before/after counts, failures and remaining risk.
Problem-shaped proof paths
The shortest trust path is not a generic portfolio tour. Pick the page that matches the buyer's current risk: supplied design fidelity, local landing performance, internal ops, paid-media tracking, missing leads, unreliable automation, checkout friction, report mismatches or mobile MVP architecture.
For supplied Figma designs that need faithful WordPress implementation, responsive polish, editable sections and project CMS handoff.
open Figma WordPress proofFor AppSheet or Google Sheets systems with reception flow, room status, consumption, cash close, inventory and reports by unit.
open AppSheet ops proofFor WordPress/Elementor landing pages that need local-service UX, form/CTA tracking, SEO/schema and PageSpeed acceptance.
open landing proofFor public lead paths where booking, menu, quote or form blockers need evidence before a redesign.
open website audit proofFor forms, notifications, booking paths and SMTP/log checks where a buyer needs before/after evidence.
open form rescue proofFor dropped events, duplicates, retries, destination mismatches and workflow acceptance checks.
open workflow proofFor checkout blocks, payment or shipping boundaries, order mismatches and safe no-purchase evidence.
open checkout proofFor custom checkout tracking where events, values, dedupe keys, UTMs and buyer-exclusion audiences must be validated before campaign changes.
open tracking QA proofFor resident requests, maintenance queues, vendor work, board approvals, status tracking and logs.
open HOA ops proofFor technical buyers who need role flows, API/state choices, offline-safe drafts and iOS/Android validation before scope grows.
open mobile MVP proofFor sales, finance and ops buyers who need source rows, rejects, totals and dashboard checks to match before decisions.
open reporting proofDelivery packets
The public portfolio now foregrounds the type of result, the evidence left behind, and the limits that keep the job from becoming open-ended support.
Broken form, checkout, booking, responsive layout, CTA path, plugin conflict, launch QA or small redesign slice.
n8n, Make, Zapier, webhook, CRM routing, WhatsApp-safe flow, retries, duplicate handling, logs or dry-run review.
CSV/Excel cleanup, CRM import QA, KPI mismatch, store totals that do not match, dashboard bug or report sanity check.
Base44, Lovable, Supabase, OpenAI/Anthropic wiring, prompt workflow, fallback, approval step, app QA or launch readiness.
Portfolio examples
Public proof-of-process cards: no fake client names, no fake results, just the types of scoped work that are easy for a buyer to recognize and review.
Ops menu
Python or JavaScript utilities for CSV/JSON cleanup, APIs, file processing, imports, exports, and repeatable local tasks.
Imports, formulas, dedupe, validation tabs, Apps Script runs, status logs, and owner-friendly handoff for spreadsheet workflows.
HTML/CSS/JavaScript bugs, WordPress pages, broken dashboard states, responsive cleanup, browser checks, exports, and targeted UI behavior repairs.
Mobile CTA, contact form, booking, menu, WhatsApp, public profile link, and multilingual path checks for small-business sites.
n8n, Make, Zapier, Airtable, CRM, webhook, API, and AI workflow checks for retries, mapping, dedupe, logs, and handoff.
Small admin tools, prototype screens, intake flows, operational utilities, and first-pass systems that make a messy process reviewable.
Plain-English checks for prices, products, paid orders and dashboard totals that do not match across a store, sheet, app or internal panel.
Admin screens, charts, tables, filters, exports, responsive regressions, accessibility gaps, and browser evidence for review.
Reproduce a problem, isolate likely causes, capture logs or screenshots, apply a focused fix, and summarize what changed.
Focused connectors around CRMs, ERPs, dashboards, admin panels, private APIs, browser workflows, and exported files.
Pre-import checks for contacts, deals, owners, stage mapping, duplicates, rejected rows, and handoff-ready cleanup reports.
Calculators, intake widgets, quote forms, and JavaScript tools that can live inside existing sites.
Runbooks, agent instructions, validation gates, prompt templates, and handoff structure for teams using AI-assisted delivery.
Checkout, booking, payment plugin, cache, email, webhook, theme, and admin-flow debugging with clear evidence and rollback notes.
One endpoint reliability pass with payload shape validation, timeout/retry behavior checks, duplicate handling, and rerunnable diagnostics.
Handoff format
Good inputs are a repo, file, sample rows, endpoint docs, browser error, screenshot, or a minimal reproduction. I prefer sample or staging data first, then production only when the scope is clear and access is appropriate.
input: sample rows / staging URL / exported file
task: isolate one failure mode
ship: patch, script, workbook, or report
check: command, screenshot, rows, or browser pass
risk: what still needs real data or production access
Proof format
Every job should end with a clear artifact, a repeatable check, and a short note that makes the next handoff easy. The goal is not to show decoration; it is to prove that the core risk was understood and tested.
FastAPI endpoint, Playwright flow, JSON response, screenshots, logs, and run command.
open sample artifactPlain JavaScript, editable inputs, clear element IDs, responsive pass, and install note.
open sample artifactBefore and after rows, validation counts, rejected rows, and a command that can be rerun.
open sample artifactRequired fields, duplicate keys, stage mapping, owner gaps, invalid amounts, rejected rows, and rerunnable checks.
open sample artifactRepro steps, impact, browser evidence, acceptance checks, and a prioritized fix path.
open sample artifactViewport, duplicate IDs, table overflow, chart sizing, icon labels, status feedback, and handoff notes.
open sample artifactMobile CTA, form, booking, menu, public profile link, language path, and broken-link checks.
open visual proofWebhook/API payloads, mapping, retries, dedupe, logs, fixtures, and handoff notes for automation delivery.
open sample artifactPublic-sector opportunity triage sample with summary, fit score, requirement matrix, red flags, questions, response outline, and go/no-go recommendation.
open offer routeVisual first pass for prices, products, paid orders and dashboard totals that do not match across a store, sheet, app or internal panel.
open sample artifactSheet sync skeleton, duplicate protection, status logging, and setup notes for a safe first pass.
open sample artifactSample-to-full workflow map, imports, dedupe, formulas, reject rows, run logs, acceptance checks, and handoff notes.
open sample artifactInstruction cleanup, validation gates, failure-mode notes, task templates, and a measurable handoff loop.
open sample artifactCheckout, booking, cache, payment gateway, webhook, email, theme, and plugin-conflict checks with a safe handoff.
open sample artifactCart, checkout, app, discount, shipping, tracking, Klaviyo, mobile, console, and handoff checks for money-adjacent bugs.
open sample artifactEndpoint smoke pass, payload validation, timeout/retry behavior, idempotency checks, and a rerunnable diagnosis package.
open sample artifactGitHub projects
These repositories show the same delivery pattern used in paid work: focused scope, working files, validation path, and reviewable output. They are small on purpose so a buyer can understand the shape quickly.
Playwright smoke checks, console capture, overflow checks, screenshots, and Markdown report output.
open qa-smoke-report-kitGoogle Sheets sync flow with duplicate protection, status normalization, logs, and handoff notes.
open apps-script-sheet-syncPython CSV audit for workflow runs with retry, dedupe, error-code, slow-run, and handoff-ready reliability checks.
open workflow-reliability-check-kitPython endpoint checks with JSON plans, status/timing assertions, Markdown/JSON/CSV reports, fixture server, tests, and handoff notes.
open api-health-check-kitPython CSV audit for CRM/RevOps imports with required fields, duplicates, stage mapping, rejects, JSON summary, tests, and handoff notes.
open crm-import-qa-kitDependency-free Node audit for dashboard snapshots with before/after fixtures, responsive checks, tests, and handoff notes.
open dashboard-bugfix-playbookDependency-free Python audit for small-business websites covering CTA, contact, booking, canonical, viewport, and handoff-ready lead-path reports.
open website-lead-recovery-check-kitOperating rules
Start focused
A useful first message includes what is broken, what should happen, a sample file or URL, and any deadline.