FAQ

For a diagnostic audit: structural metadata — module and field definitions, workflow rules, blueprint stage definitions and transitions, custom and scheduled functions, Zoho Flow connections, and the relationship structure between modules. Not transactional business data — individual records, contact details, deal values. The goal is a map of how your system is built, not a copy of what's in it.

For a Build & Verify engagement, the Workbench also includes seeded test data and the process scenarios we're testing against, plus whatever's coming out of the Shop's script library as a starting point.

A diagnostic audit is strictly read-only — I query your Zoho environment through its APIs, and nothing is created, modified, or deleted. A Build & Verify or Fix & Remediation engagement does eventually change things, but only after you've approved the specific change; all the design and testing happens against seeded data in the Workbench first, not live in production.

Diagnostic extraction currently covers Zoho CRM, Zoho Recruit, and Zoho Flow (including a dedicated Connections audit). Build, fix, and development work draws on a much broader script library in the Shop — CRM, Flow, Books, Bookings, Creator, Projects, Inventory, WorkDrive, Desk, Sign, and more. If your work touches an app that isn't listed, mention it when you get in touch and I'll let you know where things stand.

There are two options — you choose whichever you're more comfortable with.

Option 1 — Zoho Assist (remote session). You establish a remote connection to your browser using Zoho Assist, and I log into your Zoho environment through that session. You never share a password, and your MFA setup stays entirely on your side. I do what I need to do, and the session ends.

Option 2 — Credentials with Settings access. You provide login credentials for a Zoho user that has access to Settings. Standard admin-level visibility is sufficient.

I treat all client system information as confidential — full details are in the Privacy Policy and Terms of Service.

Depends on the engagement. A focused diagnostic audit typically moves in days once access is confirmed. A Build & Verify engagement or a complex fix is scoped individually — I'll give you a realistic timeline as part of the quote, based on the size of your system and the depth of the work.

For a diagnostic audit: interactive visualizations of your system's structure, the underlying structured metadata, and a plain-language written findings summary flagging anomalies, gaps, and items worth attention.

For a build or fix: tested Deluge functions and workflows, verified against your scenarios, plus a written summary of what was built or changed and why.

Either way, the Workbench itself can be handed off as documentation. See the Sample Workbench page for a closer look at what a diagnostic deliverable looks like.

Yes. The visualizations are designed to be readable without a technical background, and the written findings summary interprets the output for you directly in plain language — you don't need to touch an AI tool or the raw metadata yourself to get value from an audit.

I do. AI is part of how I work, not something handed to you to run yourself — the Shop's context files are what make that AI output reliable in the first place, and that's not something I hand over separately from the engagement.

Generally high, but with a known edge case worth understanding: field references get identified by analyzing the Deluge code directly. Most field references are captured reliably. When a field's API name is constructed dynamically — for example, by concatenating string values at runtime — that reference can be missed.

This is a disclosure, not a disclaimer. If you identify a genuine gap caused by this limitation, flag it and I'll rerun the relevant analysis at no charge.

Sometimes the most useful thing a small-system audit turns up is what's missing — fields that were never mapped to a workflow, stages that have no exit condition, automations that were planned but never built. A clean system is still worth documenting, especially before it gets complicated.

If you're genuinely unsure whether the scope fits, get in touch and describe your setup — I'll give you a straight answer.

Early is actually the best time. A baseline Workbench in the first 90 days gives you a clean reference point before complexity accumulates — so 12 months from now, when something goes wrong, you're diagnosing against a known-good starting state rather than guessing what changed.

It also means your system is documented from the start. That matters the first time a staff member leaves or a consultant hands off.

Yes. An inherited system with layers of undocumented automation, renamed fields, overlapping workflows, and logic that nobody can fully explain is exactly what a diagnostic Workbench is built for. The extraction tells me what's there. The analysis tells me what it means — I don't need anyone to explain it to me first.

Every engagement is scoped individually after a short conversation, because a diagnostic audit on a 15-module CRM and a Build & Verify project spanning three Zoho apps aren't comparable work. Message me on Upwork, describe what's going on, and you'll get a clear, custom quote before anything moves forward. See Services & Engagements for what each engagement type typically includes.

Right now, yes — Upwork is the only channel I'm using for new client communication. Message me there and I'll review your situation, respond within one business day, and scope an engagement from there.