Does it work with our existing FreshBooks licenses?
Yes — the adapter rides on top of your existing FreshBooks subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Fresno, California. After go-live, the FreshBooks adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
Can the FreshBooks adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your FreshBooks tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The FreshBooks adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
How long does the FreshBooks integration take to ship?
Our standard window is thirty days from signed scope to live FreshBooks adapter in production, plus a one-week monitored stabilization phase. For Fresno, California, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What happens if FreshBooks changes their API after we go live?
Our SRE team monitors FreshBooks change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.