A roof photo and a utility bill model the array layout, shading loss, and expected annual production against the roof's remaining service life. Priced the way the trade already prices — new work by system size in DC kilowatts; detach-and-reset per module, with roof squares quoted by the roofer. Booking, dispatch, proof of work, the invoice and the settlement are one record, from the first call to the last dollar.
A roof photo and a utility bill model the array layout, shading loss, and expected annual production against the roof's remaining service life. Ask for it in plain language; the workspace does the part that is the same every time, and leaves you the part that is judgement.
Homeowners re-roofing over an array nobody else will touch arrives through a form, a call, a text or a referral, and lands as one contact with one history — not four copies in four inboxes. The call is recorded, transcribed and filed against them.
The quote is built on new work by system size in DC kilowatts; detach-and-reset per module, with roof squares quoted by the roofer. Two people pricing the same job get the same number, because the basis lives in the workspace and not in somebody's head.
Accepted work becomes site record: roof plane, pitch, azimuth, shading, remaining roof life on a schedule, assigned to a real person with the drive time, the parts and the access notes already attached.
Site record: roof plane, pitch, azimuth, shading, remaining roof life is captured in the field, timestamped and located, and lands in the customer's own portal before the crew is off the property.
The invoice is generated from the closed job, not retyped from it. Card, ACH and financing sit inside the document, and every dollar — including what a referral partner is owed — is written to the XODIAK ledger.
Every solar installation, service & detach-reset operation eventually runs on the same four things: a calendar, a phone, a notebook and someone's memory. They work until the business is big enough that they cannot, and the failure is always the same — the thing that was true in the field never reached the office.
None of that is a discipline problem. It is what happens when the estimate, the schedule, the photos and the invoice live in four systems that do not know about each other.
A roof photo and a utility bill model the array layout, shading loss, and expected annual production against the roof's remaining service life.
It does not set your prices. Quantities come from what was actually measured or counted; the rates come from your own book. That is the difference between a tool that guesses and a tool that shows its work — and it is why two people on your team pricing the same job land on the same number.
This is not an app that integrates with five other apps. It is one data spine — the customer, the job, the money — that every module reads and writes. xSOLARx inherits the operating core every service business needs, then adds what solar installation, service & detach-reset specifically requires.
Contacts, companies, and every deal in a pipeline you can see down. The customer record is one record, not one per app.
One calendar for crews, customers and you. Availability, booking links, drive time and the jobs themselves in the same grid.
Assigned work with a due date and an owner, hung off the customer and the job rather than a group chat.
The work order is the spine: scheduled, dispatched, documented, closed and billed as one object, never re-keyed.
Your customer's own view: what was scheduled, what was done, the photos, the quote, the invoice, the receipt. No login support calls.
Invoice from the closed job, with the line items the job produced. Terms, reminders and aging that chases itself.
Card, ACH and financing at the moment the customer says yes — in the quote, in the portal, and in the field.
Email, SMS and voice against the same contact record, so the whole thread is one thread whichever way the customer replied.
Reach the list you already have — seasonal reminders, renewals, win-backs — with the outcome attributed back to the job that paid for it.
The ledger. Every dollar of revenue, cost and referral credit written to a chain you can audit, with settlement attached.
What is on the truck, what is in the shop, and what has to be ordered — tied to the jobs that will consume it.
Suppliers, price books and purchase orders with the real cost of a job attached to the job, not to the month.
The numbers behind the business, read off the records you already keep. No spreadsheet export, no separate BI seat.
A shared, permissioned room for a big job: documents, scope, questions, approvals and signature in one place.
Referral sources, subcontractors and channel partners with the revenue share calculated and settled, not remembered.
Work that is about to exist — permits, closures, weather, listings, filings — matched against what you sell and where you sell it.
Every photo, video and voice note the business has taken, organised by job and customer instead of by whoever's phone took it.
A scaffolded xSOLARx workspace opens with these already in it. Not empty tables waiting for a consultant — the records, the workflows and the integrations this trade runs on.
Every one of those lines is a revenue type the workspace can price, schedule, document and invoice on its own terms — recurring contracts do not get bolted onto a one-off quote form.
Most solar installation, service & detach-reset businesses find work after somebody else has already decided to buy. The platform's signal layer looks earlier — at the public record, and at what a camera can see from the road.
Permits, filings, closures, listings, weather events and WARN notices, matched against what you sell and the territory you sell it in. Dated and sourced, so you can act on it rather than believe it.
The platform's drive-by layer reads public street-level and camera imagery and catalogues what it finds as a located, described condition — an asset in a state somebody eventually has to deal with. It tells you the need exists. Whether you want it is still your call.
A signal that matches a customer you already have does not arrive as a new lead. It arrives on the record it belongs to, which is the difference between a useful alert and another inbox.
Drive-by intel is a platform capability, not a lead subscription. It is described here because it is how xSOLARx finds work; it is not a promise of a volume of jobs. See the drive-by layer.
xSOLARx is not sold as a seat licence with a floor you have to grow into. The workspace scaffolds, you run it, and the premium surfaces unlock individually — either on a monthly unlock or against a credit balance you top up when you want to.
Prices shown are the live platform catalogue. xSOLARx-specific packaging is set per market; ask before you assume a number you saw somewhere else applies to you.
Every xVERTICALx on this network — xSOLARx among them — is a face wrapped around the same engine. The leading and trailing x are platform brackets: Cross-Connect Protocol in, Cross-Connect Protocol out.
Cross — bridge any vertical to any resource. Connect — one identity, one ledger, one settlement rail. Protect — verified identity and an auditable chain from edge to core. See all 74 verticals.
No. xSOLARx is the solar installation, service & detach-reset configuration of the Biz Dev App — the same platform, the same ledger, the same support, scaffolded with the 17 modules and 6 record types this trade actually uses. If the business later adds a second line of work, it does not mean a second subscription; it means another vertical switched on in the same workspace.
On new work by system size in DC kilowatts; detach-and-reset per module, with roof squares quoted by the roofer. The basis lives in the workspace rather than in an estimator's head, so the same job quoted by two people produces the same number. Your own rates, your own catalogue — the platform supplies the structure and the arithmetic, never the prices.
Utility interconnection portals, Inverter and monitoring platform APIs, Permit portals, QuickBooks, Stripe are wired first, because those are what a solar installation, service & detach-reset business is usually already running. Anything else goes through the xCONNECTx public API catalogue rather than a custom build.
It comes in. The archive import pipeline takes historical customers, jobs and invoices and lands them as real records — searchable, reportable, attached to the right customer — rather than as a folder of PDFs nobody opens. The point of moving is to keep the last five years, not to start over.
Not a demo with sample data. Bring a customer you already have, quote the work on new work by system size in DC kilowatts; detach-and-reset per module, with roof squares quoted by the roofer, run it, and see whether the invoice writes itself.