FAQ
Buyer FAQ and answer hub for ClaraOps.
Direct answers for practice owners evaluating fit, SimplePractice and Google Workspace workflows, payroll-provider boundaries, compliance support, onboarding, pricing, privacy, support, and when ClaraOps is not a fit.
Quick answers
Direct answers for practice owners
What is ClaraOps?
ClaraOps is a payroll-readiness review layer for practice owners: it organizes source evidence, exceptions, approvals, workpapers, and handoff records before payroll decisions are final.
See the product workflowDoes ClaraOps replace my payroll provider?
No. ClaraOps does not run payroll, file payroll, move money, submit payroll taxes, or replace your payroll provider, accountant, attorney, HR advisor, or final owner review.
Review the boundariesHow does ClaraOps work with SimplePractice and Google Workspace?
ClaraOps works from practice-authorized SimplePractice exports and customer-controlled Google Workspace records, then keeps source status, exceptions, notes, and handoff context visible for review.
Check integrationsDoes ClaraOps help with compliance?
ClaraOps can make source-data limits, exception status, review decisions, and handoff records easier to see, but it does not provide legal, tax, HR, accounting, payroll-provider, or compliance advice.
Read compliance limitsWho is ClaraOps for?
ClaraOps is for therapy, behavioral-health, or similar service practices using SimplePractice and Google Workspace that want cleaner payroll-readiness review without handing final decisions to software.
Read the FAQBuyer questions
Answers before you start
What does ClaraOps do?
ClaraOps organizes payroll-readiness evidence, source status, exceptions, review notes, approval checkpoints, and handoff records so a practice owner can review payroll work before payroll is run elsewhere.
Walk through the productDoes ClaraOps replace payroll?
No. ClaraOps is not a payroll processor, tax filer, HR/legal/compliance advisor, or guarantee of payroll accuracy. It helps prepare and review the handoff; your payroll provider, accountant, advisor, or owner review remains responsible for final decisions.
Review the boundaryWhat do I upload?
After sign-in, ClaraOps expects practice-authorized, payroll-relevant source exports and review context such as SimplePractice reports, owner-approved adjustment notes, roster context, and handoff workpapers. Public pages collect only non-sensitive fit and contact details.
Use the setup checklistWhat should stay out of public forms or email?
No PHI, payroll files, employee SSNs, credentials, raw payroll rows, or sensitive compliance details belong in public forms or routine email. Keep sensitive material inside the reviewed, protected workflow after access is set up.
Read security boundariesHow long does setup take?
Setup depends on source readiness: confirm fit, review the checklist, gather the right exports and handoff notes, then work through the first owner-ready review. ClaraOps sets expectations for a careful rollout instead of promising instant automation.
Review setup expectationsWhat if SimplePractice exports are messy?
Messy exports are expected. ClaraOps can flag stale records, missing evidence, unusual pay, adjustment questions, and review blockers, but it cannot make incomplete source data correct without customer review.
See source-data guidanceWho reviews final payroll?
The practice owner, delegated operator, accountant, bookkeeper, payroll provider, or other authorized reviewer still reviews the final handoff. ClaraOps makes the evidence easier to inspect; it does not remove the decision-maker.
See approval checkpointsWhat happens after I sign in?
You move from public guidance into a protected company workspace, follow setup prompts, connect or upload approved source context, review exceptions, and prepare the first owner-ready payroll handoff before any payroll is run elsewhere.
Start or request accessWhat support exists?
Support helps with setup and workflow questions after the public pages answer fit, pricing, setup, and boundaries.
Review support optionsWho can access data?
Access belongs to authenticated company users, owner-approved delegated operators, and reviewed support paths. Public marketing pages never expose private payroll rows, PHI, credentials, employee SSNs, or customer artifacts.
See access postureHow do export, deletion, and retention requests work?
Export, deletion, and retention requests are reviewed account workflows, not public-form promises. ClaraOps avoids unreviewed instant purge or legal commitments on public pages and routes data requests through the protected account/support process.
Read privacy postureWho is ClaraOps for?
ClaraOps is for therapy or healthcare practices that already run payroll elsewhere but need a calmer way to organize SimplePractice exports, Google Workspace workpapers, exception notes, review status, and owner handoff context before payroll decisions are final. Start with the /product workflow if you want the full path.
How does ClaraOps fit with SimplePractice and Google Workspace?
How do integrations handle SimplePractice and Google Workspace? ClaraOps works from practice-authorized SimplePractice exports and customer-controlled Google Workspace destinations when configured. The /integrations page explains the fit: ClaraOps does not scrape SimplePractice, read arbitrary Drive files, bypass source permissions, claim official partnership, or send exports without user action.
Is ClaraOps my payroll provider?
Can ClaraOps change payroll or send anything without us? No. ClaraOps organizes payroll-readiness evidence, exception lists, review status, and handoff context. It does not run payroll, file payroll, submit payroll taxes, move money, or replace the payroll provider, accountant, attorney, HR advisor, compliance advisor, or final owner review.
Does ClaraOps give compliance, tax, legal, accounting, or HR advice?
No. ClaraOps can make review blockers and source-data questions visible, but it does not provide legal, tax, accounting, HR, payroll-provider, compliance, clinical, or medical advice. The /compliance page explains the support boundary in buyer-safe language.
What if source data is wrong?
FAQ source-data answer references reconciliation limits: customers remain responsible for the accuracy, completeness, timeliness, and authorization of source records. ClaraOps can flag stale exports, missing evidence, unusual pay, adjustment questions, and review blockers, but it cannot make incomplete source data correct without customer review. See /resources for the source-data quality guide.
What does onboarding require?
Onboarding requires practice-authorized source material, a named owner or delegated operator for review decisions, Google Workspace destination choices if used, and agreement on what should stay outside public demo/support paths. The /demo page keeps the first conversation workflow-level, not a request for PHI, payroll files, employee SSNs, credentials, or raw payroll rows.
How does pricing work?
The /pricing page explains current paid-beta positioning and fit expectations without promising guaranteed savings, guaranteed payroll precision, or unlimited support. Pricing questions should stay tied to practice size, payroll cadence, workflow complexity, and whether ClaraOps is the right review layer.
Who can see our payroll or practice data?
Can staff or support access our data? Payroll and practice operations data stays inside secure company routes. Access is tenant-scoped for authorized owners or delegated operators, and sensitive support access requires consent or reviewed break-glass approval. Start with /security and /legal/privacy for the public trust posture.
What can buyers ask before a demo?
Buyers can ask about workflow fit, SimplePractice and Google Workspace source categories, owner-review steps, pricing fit, security posture, support expectations, and onboarding readiness. Public pages and demo forms should not include PHI, payroll files, employee SSNs, credentials, raw payroll rows, or sensitive compliance details.
Can we export or delete our data?
Export, retention, deletion, and backup-window requests are reviewed workflows so records stay accurate. ClaraOps does not promise instant purge, unreviewed self-service deletion, or public download of private payroll artifacts. Review /legal/privacy for the public posture.
Where should security questions go?
Start with the /security trust page, /legal/privacy posture, /legal/terms responsibility boundaries, and support expectations below. During beta, routine support goes through brent@claracaps.com, while security, privacy, or vulnerability reports go to security@claracaps.com without sensitive files or exploit payloads in public email.
When is ClaraOps not a fit?
ClaraOps is not a fit if you need a payroll processor, tax filer, HR/legal/compliance advisor, emergency payroll rescue service, direct SimplePractice write-back, unreviewed automated payroll decisions, or a public upload path for sensitive payroll files. It is a review and handoff layer for practices that can keep owner review in the loop.
Support
Public support model
Public support copy sets conservative expectations for paid beta and does not create SLA, warranty, unlimited-support, emergency-coverage, or professional-advice commitments.
Routine support
Routine support goes through brent@claracaps.com during paid beta, with business-day support during normal U.S. Central Time business hours and an initial routine support acknowledgement target of two business days.
Security and privacy escalation
Security, privacy, or vulnerability reports go to security@claracaps.com and should avoid payroll files, PHI, employee SSNs, credentials, raw payroll rows, exploit payloads, or sensitive customer data in public email.
Payroll-cycle escalation
Payroll-cycle escalation means triage and next-step guidance, not a guarantee that ClaraOps can rescue a payroll deadline, run payroll, or make final decisions.
Advice boundary
Support does not provide legal, tax, accounting, HR, payroll-provider, compliance, clinical, or medical advice.
Contact paths
Safe contact and support handoff
Use the right public contact path for sales or fit questions, routine product support, and security or privacy concerns. Public email is for non-sensitive coordination only.
Public support paths are for non-sensitive coordination only. Do not include PHI, payroll files, employee SSNs, credentials, raw payroll rows, or sensitive compliance details in public email.
Sales or fit questions
Ask whether ClaraOps fits your practice, pricing, source systems, paid-beta scope, setup timing, or next step. Keep the message high level and non-sensitive.
Email support@claracaps.com about fitRoutine product support
Use routine support for setup questions, checklist clarification, access handoff, or product workflow confusion. Two-business-day acknowledgement target for routine support and security/privacy triage.
Email support@claracaps.com for supportSecurity or privacy concern
Use the dedicated security/privacy contact for suspected vulnerability, unauthorized access, privacy concern, or sensitive-data handling question. Do not include sensitive files or credentials in public email.
Email security@claracaps.comBuyer-safe email templates
Use one sentence about your practice type, source systems, and question. Do not include PHI, payroll files, employee SSNs, credentials, raw payroll rows, or sensitive compliance details in public email.
What to expect
ClaraOps routes sales, fit, support, security, and privacy questions to the right non-sensitive handoff path. Sensitive onboarding material waits for the protected workflow and reviewed customer authorization.