Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the USPS surface.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Springfield, Illinois. After go-live, the USPS 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.
How long does the USPS integration take to ship?
Our standard window is thirty days from signed scope to live USPS adapter in production, plus a one-week monitored stabilization phase. For Springfield, Illinois, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
What happens if USPS changes their API after we go live?
Our SRE team monitors USPS 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.
Can the USPS adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your USPS tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
Do we own the integration code at the end?
Yes. The Connectify USPS adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.