Oblyss runs the job on its own. The rest just plugs in.
One job record, fed from every side
The connected job record
Most platforms sell you the integration because the core is thin. We built the core.
Estimates to signed contracts
Build the estimate, present Good, Better, Best tiers, and capture a native signature on the pad or by link. Signing lives on the platform, with no third-party redirect and no per-signature fee.
Scheduling and dispatch
A drag-and-drop board, route optimization, and a live dispatcher map, built in.
Online payments
Stripe-powered. Collect deposits and milestone draws that settle on your own connected Stripe account, tied to your pipeline stages.
Field documentation
A native drawing tool, a photo annotator, pier logs, and elevation surveys, no separate subscription required.
AI call answering
Retell-powered. Missed and after-hours calls answered around the clock, logged straight to the customer timeline.
Reporting and BI
Reporting and BI KPI dashboards, an AI business briefing, and a custom report builder, without exporting to a spreadsheet.
Every tool that does not talk to the others gets paid in your office manager's time.
The tech shoots photos in one app. The office logs the call in another. Accounting re-types the invoice into the books. The pier diagram lives in a drawing tool nobody in the office can open. Each handoff is a chance to fat-finger an address, miss a payment, or lose the one photo that would have settled a warranty dispute.
Integrations are supposed to end that. Too often they just move the mess around. The difference here is that Oblyss owns the record. A connection does not create a second version of the truth. It writes to the one that already exists: the job. Photos land on it, calls log to it, expenses pull into it, payments post against it.
The test for any connector
What connects, and what it does for the job.
Accounting and payments
QuickBooks
Full two-way sync is live today through QuickBooks Desktop: invoices and customers push over, expenses and paid-invoice status pull back on a daily schedule or on demand, with a sync dashboard and error log. QuickBooks Online sync is still activating. Either way, your books and your jobs stop disagreeing.
STRIPE
Connected-account onboarding so deposits and milestone payments settle on your own connected Stripe account, not a middleman's. Card and ACH steering and optional surcharge pass-through are built in.
Calls, leads, and referrals
CallRail
Inbound and outbound calls log to the contact timeline. A brand-new caller auto-creates a contact and a pipeline job with the source attached, so no lead falls through because someone was busy.
LEAD INGESTION API + META LEAD ADS
Generate an API key and ingest URL to receive leads from Angi, Google Local Services, your website form, or an automation tool. A dedicated Meta Lead Ads webhook pulls Facebook and Instagram lead forms in the same way. Every lead lands tagged with its source for honest attribution.
RETELL
The AI engine behind AI Voice Answering. Answers after-hours calls, books the concern into a lead, and logs the full conversation to the contact timeline.
Get The Referral
Referral leads ingest by webhook, and job status updates push back, so your referral partners see progress without a phone call.
Outbound webhooks
Subscribe your own endpoints to platform events like lead created, job status changed, estimate sent, and payment received. Signed payloads with a delivery log, for the automations you already run.
TWILIO
The SMS and voice infrastructure behind group texting, text automations, and call logging. Nothing to configure on your end, it just runs underneath the features you already use.
RESEND
The email delivery infrastructure behind receipts, warranty certificates, and notification emails, so they land in an inbox instead of a spam folder.
Field and documentation
CompanyCam
Photos your techs shoot from the field app sync to the matching project, so the job record and your photo library never drift apart. Required-photo tasks still cannot be skipped.
ArcSite
For firms that need engineered drawings, ArcSite proposal exports attach to the job and its line items, payment schedules, and bill of materials import back with cost fields for margin visibility. Oblyss also has a native site sketch tool for teams that do not need the full drawing suite.
Marketing and territory data
Google Analytics 4 and Google Ads
Capture the click identifier on inbound leads and push closed-job revenue back to GA4, so Smart Bidding optimizes for paid jobs, not form fills.
Permit data: Shovels and PermitStack
Per-job permit history plus territory-wide structural and foundation permit signals feed the Lead Signals inbox and the Job Heatmap. A permit filed nearby is a homeowner already spending on their foundation.
BatchData and Lob
Neighbor addresses pulled and postcards verified, printed, and mailed for the Direct Mail Engine, launched from the job your crew just finished. Per-piece cost shown before you confirm.
Calendar, commissions, and migration
GOOGLE CALENDAR
Each branch connects its own calendar and appointments sync with write-back, with echo-loop prevention so you do not get duplicate events. Multi-location shops stop fighting over one shared calendar.
MICROSOFT OUTLOOK — STATUS TO CONFIRM
Outlook calendar sync is on the roadmap alongside Google Calendar. Live connection status is being confirmed before this is listed as active.
PER4MANCE.IO — STATUS TO CONFIRM
The Commissions ledger and rules engine run natively either way. A Per4mance.io sync is planned as an optional add-on; final connection status is being confirmed.
Salesforce migration
A one-time migration framework reads your Salesforce data and imports it into Oblyss during onboarding. Bring your history with you when you switch.
CSV and platform imports
Import contacts and jobs by CSV, or migrate from MarketSharp or Go High Level, so your first day on Oblyss starts with your real book of business, not a blank slate.
GUSTO, ADP, AND PAYCHEX
Weekly payroll exports to whichever of the three you already run, so commissions and hours flow out of Oblyss instead of getting rebuilt by hand every week.
Watch a single job pull from every connection without a soul re-typing a thing.
A call comes in and logs itself to a new contact with its source. The tech shoots photos that sync to the record. The estimate is signed natively on the pad. Payment settles on your own account. The invoice posts to your books overnight. A permit filed next door lights up the Lead Signals inbox. None of it was entered twice.
That is what native-first buys you. The integrations are not the product. The connected job record is the product, and the integrations keep it fed.
Job #4821 · activity
Illustrative activity feed.
Frequently asked questions
Do I have to connect anything to get value out of Oblyss?
How does the QuickBooks Online sync actually work?
Where do payments settle?
On your own connected account. Deposits and milestone payments land with you, not with a middleman holding your money. Card and ACH steering and an optional surcharge pass-through are built in. The payments page walks through the full flow.
I use ArcSite for drawings. Do I have to give it up?
Not at all. If your firm needs engineered drawings, keep ArcSite: its proposal exports attach to the job and its line items, payment schedules, and bill of materials import back with cost fields for margin visibility. If you only sketch pier layouts, the native site sketch tool may cover you without a second subscription. Use whichever fits.
Can I bring my existing data when I switch?
Yes. Import contacts and jobs by CSV, use the lead ingestion API, or run a one-time migration from Salesforce, MarketSharp, or Go High Level during onboarding. The goal is to start your first day with your real book of business. See data migration and onboarding for how the guided process works.