QuickBooks invoices ingested via Zoho SDK APIs
Invoices, customers, and products created as correctly related records in Zoho CRM from QuickBooks data, with no manual re-entry.
CRM developer and functional lead who owns the platform end to end.
I work across CRM development, administration, architecture, and integrations, with deep specialization in Zoho One. I take a business requirement from discovery through data modeling, automation, custom development, integration, migration, testing, deployment, and support. One owner across the full lifecycle, without the handoff gaps between functional and technical teams.
Zoho One · Deluge · Creator · REST APIs · JavaScript · Python · SQL · Azure
Start a conversation Resume (PDF)
End to end
Requirements → architecture → production
Zoho One
CRM · Creator · FSM · Analytics · DataPrep
Integrations
REST APIs · Zoho SDK · OAuth · webhooks
Data + Cloud
SQL · Python · Azure Functions · SFTP
What you get when I own the CRM
One person across the full lifecycle, from first stakeholder interview to post-launch support.
- Requirements and process mapping. Business requirements become user stories, process maps, and module designs before anything is built.
- Solution design. Module configuration, workflow design, segmentation requirements, and data mappings are agreed with stakeholders.
- Build. Zoho CRM workflows and automations, Deluge functions, Zoho Creator apps, Flow integrations, and SDK or REST API connections such as the QuickBooks invoice ingest.
- Testing and deployment. Managed testing and delivery in Azure DevOps, including user acceptance testing with stakeholders.
- Support and iteration. Troubleshooting data sync and integration issues with engineering and client teams, plus dashboards that keep stakeholders self-sufficient.
Results I have delivered
Outcomes from recent CRM roles, with the before and after where it matters.
48h → 18h
Inquiry response time
Automated Zoho Desk triage and routing cut first-response time by 62%.
~10 hrs / week
Saved by automation
Deluge automations in Zoho CRM, tested and delivered through Azure DevOps.
+25%
Required-field completeness
Legacy-to-Zoho migration with defined mappings, segmentation, and process structure.
12 hrs / month
Manual reporting eliminated
Stakeholder-facing dashboards replaced recurring manual reporting effort.
Enterprise onboarding across three CRMs
Client tracking and CRM requirements translated into integrations spanning Salesforce, HubSpot, and Zoho CRM.
Closed-loop attribution from fragmented sources
OTT, podcast, broadcast, and digital data mapped into attribution and CRM reporting workflows.
Experience
CRM Reporting & Analytics Specialist (Contract), Healthcare Solutions Company
- Owned Zoho CRM administration and process optimization for healthcare and clinical-research participant workflows.
- Built and maintained multi-stage participant lifecycle automation across Zoho CRM, Forms, and Analytics, from consent through qualification, secondary screening, referral, and downstream tracking.
- Built scheduled Azure Functions pipelines for encrypted CRM data extraction, transformation, and SFTP delivery.
- Ran analytics, integrations, CRM troubleshooting, UAT and change control, and cross-functional requirements across business and technical stakeholders.
CRM Systems Administrator, Ad-Apt
Own the Zoho CRM build: business requirements into workflows, automations, and module configuration. Built the QuickBooks invoice ingest on Zoho SDK APIs and Deluge automations that save the team about 10 hours every week, with testing and delivery run through Azure DevOps.
CRM Integration & Attribution Specialist, LeadsRx
Led enterprise onboarding across Salesforce, HubSpot, and Zoho CRM, and mapped fragmented OTT, podcast, broadcast, and digital sources into closed-loop attribution and CRM reporting. Partnered with engineering and client teams to resolve pixel firing, data sync, and integration issues.
CRM Systems Manager, Modofi
Ran the legacy-to-Zoho CRM migration, defining data mappings, segmentation, and process structure, lifting data quality 25%. Designed automated Zoho Desk workflows that cut inquiry response time from 48 hours to 18, and built stakeholder dashboards that removed 12 hours of manual reporting a month.
Four projects, owned end to end
Deep cuts, not brochures: the architecture, the decisions, and what changed. The rest of the archive follows below.
01 · CRM + Field Service architecture
Home services: one data model for CRM, field ops, and billing
A home services company ran customers, service locations, installed equipment, location-specific pricing, field-service activity, and recurring billing as disconnected records and spreadsheets. I designed a connected Zoho CRM + FSM architecture: Accounts own Service Locations, Locations own Machines / Equipment, Work Orders draw location-specific Products and Pricing, and Invoices close the loop, with Deluge automations and scheduled processes driving recurring operational tasks.
Technical decisions
- Custom modules over flat records, so equipment and pricing stay queryable per location
- Location-scoped pricing instead of global price books, matching how techs actually quote
- Scheduled Deluge processes for recurring billing and operational tasks, not manual runs
Outcome
One unified business application across CRM, field-service operations, equipment management, and billing.
Zoho CRM · Zoho FSM · Deluge · REST APIs · Custom Modules · Workflows · Schedules
02 · Integration architecture
QuickBooks → Zoho: invoice ingest with zero duplicate records
QuickBooks invoice data had to appear automatically inside Zoho CRM, customer, products, and relationships intact, without duplicates and without anyone retyping invoices. I built middleware on the Zoho SDK and REST APIs around a search-before-create pattern: every customer and product is resolved by external ID before anything is created, and the CRM invoice is only written once its relationships are mapped.
Technical decisions
- Search-before-create entity resolution, so reruns and retries never duplicate records
- QuickBooks IDs stored as CRM external IDs — the idempotency key for every retry
- OAuth on both APIs with token refresh handled in middleware, not in CRM functions
- Partial-failure handling: a missing product blocks only its line, never the whole invoice
- Asynchronous ingest, so CRM users never wait on QuickBooks API latency
Outcome
Eliminated routine manual recreation of QuickBooks customers, products, and invoices inside Zoho CRM; invoice data lands correctly structured and related.
Zoho CRM · Zoho SDK · QuickBooks API · REST APIs · OAuth · Middleware · External IDs
03 · Regulated CRM platform
Healthcare CRM: participant lifecycle under change control
A healthcare and clinical-research program ran a five-stage participant lifecycle, consent through referral and downstream tracking, across many business and technical stakeholders, with sensitive participant data throughout. I owned the CRM ecosystem: administration, automation, analytics, forms, integrations, and process optimization, inside a staging → UAT → documented release pipeline with no direct production changes.
Technical decisions
- Lifecycle modeled as explicit stages with entry criteria, so bottlenecks and drop-off are measurable
- Zoho Analytics funnels on conversion, source attribution, and disqualification reasons
- Compliance-oriented SDLC: staging, formal validation, documentation, controlled release
- Encrypted scheduled exports via Azure Functions + SFTP for downstream consumers
Outcome
Analysis shifted from activity volume to downstream outcomes: where the process worked, where participants dropped out, and which sources produced quality referrals.
Zoho CRM · Zoho Forms · Zoho Analytics · Deluge · Azure Functions · UAT · Change Control
04 · Cloud data pipeline
Secure CRM data pipeline: scheduled, encrypted, hands-off
A CRM dataset had to be extracted on a recurring schedule, transformed, encrypted, and delivered to an external SFTP destination, replacing a manual export-and-send workflow. I built a scheduled Azure Functions pipeline: timer trigger, CRM API extraction, transformation, encryption at rest in transit, SFTP delivery, with failure alerting so a missed run is visible, not silent.
Technical decisions
- Serverless timer trigger over a VM cron job: no server to patch, pay per execution
- Encrypt before delivery, so files are never readable at rest on either side
- Run logging with failure alerts instead of silent cron
Outcome
A manual delivery workflow became repeatable and secure: scheduling, encryption, and external delivery handled automatically.
Azure Functions · CRM APIs · Python · SFTP · Encryption · Scheduled Jobs
More from the archive
Capabilities with production history behind them. Short version; the deep cuts are above.
Custom business applications with Zoho Creator
Operational apps with their own data, forms, workflows, and UX, built on the right layer: CRM, Creator, Kiosk, Widget, Flow, or middleware. Integrated with CRM and external systems via Deluge and REST APIs.
Zoho Creator · Zoho CRM · Deluge · REST APIs · Forms · Reports
Role-based CRM interfaces with Widgets and Canvas
Purpose-built surfaces over complex CRM environments: customer, status, last contact, next action, with Call, Schedule, and Update one click away. Built with Widgets, Canvas, JavaScript, and the Zoho SDK.
Zoho CRM · Widgets · Canvas · Zoho SDK · JavaScript · HTML · CSS
Lifecycle analytics and funnel optimization
Zoho Analytics reporting from initial leads through qualification, secondary screening, disqualification reasons, and referrals: conversion, source attribution, and bottleneck analysis instead of activity counts.
Zoho Analytics · Zoho CRM · Dashboards · Funnel Analysis · Reporting
Entity resolution and deduplication architecture
External IDs plus normalized name, domain, phone, and address matching, split into remediation of historical duplicates and prevention at record creation. Data quality as ongoing architecture, not one-time cleanup.
Zoho CRM · Data Quality · External IDs · Deduplication · Governance
Requirements-first functional architecture
Business outcome → current process → actors → data → rules → architecture → implementation, with source of truth, reporting, and downstream effects checked before building. Fewer customizations that look bigger than they are.
Business Analysis · Solution Architecture · Process Design · Data Modeling
Full-stack CRM and cloud engineering
JavaScript, Python, SQL, REST APIs, Git, Azure, Cloudflare, and Vercel alongside native Zoho. The implementation layer is chosen by maintainability, scale, security, and UX, not by habit.
Zoho · JavaScript · Python · SQL · REST APIs · Git · Azure · Cloudflare · Vercel
CRM administration & governance
Production systems stay healthy because someone owns the unglamorous parts. That someone is me.
Zoho One, in depth
CRM, Creator, Analytics, Flow, Forms, Desk, Campaigns, SalesIQ, PageSense, Canvas, and Data Prep. I know how the suite fits together, so solutions land in the right app instead of one overloaded module.
Development and integration
Deluge, Zoho SDK, REST APIs, webhooks, JavaScript/TypeScript, and Python. Recent work includes the QuickBooks invoice ingest and multi-CRM onboarding across Salesforce, HubSpot, and Zoho CRM.
Data and delivery
SQL, PostgreSQL, Supabase, BigQuery, Azure, and Azure DevOps. Migrations with defined mappings, testing with real acceptance criteria, deployments that stick.
Reporting people actually use
Stakeholder dashboards that cut 12 hours of manual reporting a month, and closed-loop attribution across OTT, podcast, broadcast, and digital sources.
Functional leadership: what happens when a stakeholder asks for a new module?
Requirements gathering, process mapping, module and workflow design, user stories, and UAT. Stakeholders get a design they signed off on before anything is built. Concretely:
- Business outcome. What are we actually trying to accomplish?
- Current process. What happens today?
- Actors. Who touches the process?
- Data. What entities actually exist?
- Rules. What can happen, and what are the exceptions?
- Architecture. CRM, Creator, Flow, Widget, middleware, or another system?
- Acceptance criteria. What has to be true for the solution to be complete?
| CRM platforms | Zoho CRM (development, administration, architecture) · Salesforce (integrations, onboarding, data workflows) · HubSpot (integrations, onboarding, data workflows) |
|---|---|
| Zoho One | CRM · Creator · FSM · Analytics · Flow · Forms · Desk · Campaigns · SalesIQ · DataPrep · Blueprint · Kiosk Studio · Widgets · Canvas · Bookings |
| Development | Deluge · JavaScript / TypeScript · Python · HTML / CSS |
| Integrations | REST APIs · Zoho SDK · OAuth · Webhooks · Middleware |
| Data | SQL · PostgreSQL · BigQuery · Supabase · Migration · Mapping · Cleansing · Deduplication · External IDs · Governance |
| Cloud / DevOps | Azure Functions · Azure DevOps · Git · Cloudflare · Vercel · SFTP · Encryption |
| Functional | Requirements · User stories · Process mapping · Solution design · UAT · Documentation · Training |
| Administration | Profiles · Roles · Field-level permissions · Sharing rules · User provisioning · Imports / exports · Release management · Support & troubleshooting |
Let's ship your CRM like it matters.
For Zoho One builds, CRM rescues, migrations, or integrations, the fastest route is email or phone.