Operations Systems & Workflow Automation Specialist | CRM Data, Excel Reporting, n8n & APIs
I help small businesses turn disconnected spreadsheets, CRM records, forms, and recurring reports into reliable operations systems.
My focus is where operations, data, and automation meet: CRM data quality, lead routing, pipeline reporting, Excel and Google Sheets automation, API integrations, and n8n workflows.
Services I provide:
• CRM data cleanup, validation, duplicate control, field mapping, and import-ready files
• Lead intake, qualification, routing, follow-up, and pipeline workflows
• Excel and Google Sheets KPI reports, dashboards, risk scoring, and recurring reporting
• REST API and webhook integrations between forms, CRMs, spreadsheets, databases, and SaaS tools
• SQL-supported data preparation, reconciliation, and operational analysis
• Error handling, review queues, test evidence, and delivery documentation
My process starts with the business rules—not the tool. I map the inputs, fields, decisions, exceptions, ownership, and expected output before building. Each delivery is tested with sample data and documented for handover.
The portfolio uses demonstration data so no client information is exposed. The workflows, dashboards, routing logic, outputs, and exception paths shown were built and tested.
Tools include Excel, Google Sheets, SQL, Python, n8n, REST APIs, webhooks, JSON, and GoHighLevel.
Most projects can be completed asynchronously through Guru messages, shared files, and recorded updates. Meetings are optional unless they are genuinely required.
Work Terms
Communication: Written-first through Guru WorkRoom. I normally respond within one business day. Short calls are optional and used only when they materially improve the project.
Project setup: Before work starts, we agree on the source files or systems, required outputs, data fields, business rules, exceptions, required permissions, milestones, and acceptance criteria.
Delivery: Work is organized into clear milestones with progress notes, test evidence, and practical documentation. Production credentials are requested only when necessary and should be shared through an approved secure method.
Payment: Hourly work can use Guru's hourly billing process. Fixed-price work should use funded SafePay milestones before implementation begins.
Scope: Corrections for defects within the agreed scope are included. New requirements or changes to the agreed workflow are estimated separately.