Where RayAccess is losing time today, what we recommend building, and the order to build it in.
RayAccess as an organization generally has well-defined processes & well-organized data. The information RayAccess needs already exists in Workforce, Jobber, QuickBooks and HubSpot. People move it between those systems by hand, and that is where most of the automatable time each week goes.
We identified 52+ staff hours per month, directly recoverable across the team, among 9 AI opportunity areas across:
The goal for RayAccess is to create breathing room for its team. We want to give the team back enough time to do the work properly rather than just keep up, and take Sergey out of the middle of every estimate. The 9 areas are grouped into 4 waves so RayAccess can start where the return is clearest instead of committing to everything at once.
We conducted 5 stakeholder interviews with leadership and staff, around 2 hours each, most of them screen-shared live:
Afterwards, we walked through every finding and number back past Sergey on a confirmation call. All ideas & proposals proved realistic & valuable, with a few slight adjustments.
Every number & figure in this AI Success Plan traces to a transcript. Where a number could not be confirmed it is marked unconfirmed rather than estimated.
Sergey owns all estimation sheets besides window cleaning & B2C and personally reviews all 6 to 8 B2B estimates a week. This bottleneck is a key limitation in sales & growth, as getting more estimates out there means more jobs.
The vast majority of these platforms have robust APIs. We just need to automatically pull from & move data around these systems.
All findings from the 5 interviews we conducted with RayAccess staff across leadership, operations, marketing, estimation, and admin.
| Pain | Cost |
|---|---|
| Weekend timesheet and productivity analysis | 2-3 hrs/wk |
| Owns most B2B estimations, and reviews every B2B estimate | 2-4 hrs/wk of review |
| Monthly KSI compilation | ~5 hrs/month |
| Pain | Cost |
|---|---|
| Disorganized asset library and unreliable photo handoff from field crews | 2-4 hrs/wk searching |
| Weekly blog and social posts produced solo from scratch | 3-6 hrs per post |
| Pulling numbers from 8-10 sources for the dashboard | ~1.5 hrs/wk, + ~1 hr for sitemap |
| Pain | Cost |
|---|---|
| Invoicing flow across Jobber, HubSpot, QuickBooks, Sheets (timesheets) and GatherUp | 4-5 hrs/wk |
| Timesheet double entry, cross-checking, & splitting hours | 2.5 hrs/wk |
| Receipts handled in several places (Drive, QuickBooks, Email, Jobber) | 2.5 hrs/wk |
| Pain | Cost |
|---|---|
| Square Takeoff exports drop square footage, so he rebuilds it for every element | Every project |
| Writes scope descriptions, then cleans them in ChatGPT, then edits again | Every estimate |
| Can only do estimations for 1 B2B service after 6 months on the job | Limits how many estimates RayAccess can get out |
Using existing tools and methodologies.
Britnie has a desktop, and the executive meetings happen in the conference room, so this has to be recorded from a phone.
"I don't have a laptop that I could take into the meetings, and we usually have the meetings in the conference room. So I don't have my computer to use it [...] as far as the meeting notes, I don't have a mobile, I just literally record on my iPhone and get the transcript from there."Britnie Escalante, HR & Admin
Today she records on her phone, pulls the transcript off manually, screenshots her handwritten notes, then rebuilds the summary in the format the team expects & updates the dashboard.
RayAccess already uses Fathom.
Zander described rebuilding an AI-generated social graphic shape by shape in Illustrator, redrawing the border and placing the icon by hand, because the edits he needed weren't possible any other way.
Claude Design removes that step, with a configurable brand & asset pack. It generates editable graphic designs instead of uneditable AI-generated images.
Britnie already runs a ChatGPT project that formats her executive summary. Ed cleans up scope descriptions, Sergey screens resumes & pulls key terms out of RFPs, Britnie reads expiry dates off COIs.
One saved project per recurring task costs nothing & makes the AI use that's already happening consistent.
~52 hrs/mo recoverable across 9 areas, sequenced into 4 waves:
| Wave | Stage | Areas |
|---|---|---|
| 1 | Quick Wins | Receipts & AP, Invoicing, Statistical Reports, Timesheets |
| 2 | Core Builds | AI Estimation Platform |
| 3 | Supporting | Weekly SEO Content, Collections, Compliance Document Tracking |
| 4 | Long Term | AI Control Tower |
Every area is tagged with 1 of 4 build types:
| Build type | What it means day to day |
|---|---|
| Headless automation | Runs in the background on a trigger. Nobody opens a new tool. |
| Assistant (Claude skill) | A person drives it, step by step. Replaces a blank page, not the person. |
| Dashboard & reminders | A screen you check, plus tasks & alerts that come to you. |
| Custom application | Real software with its own interface, built around your logic. |
"I don't want to say mindless work, but it's really important because, Lord forbid, I forget to enter a receipt. If I could just create a bill, specify what job it's for, and then maybe AI could just plug it into our expenses on Jobber. That'd be amazing."Britnie Escalante, HR & Admin
Form: Headless automation. Receipts still arrive by email, but to 1 address.
| # | Step | Who | Software |
|---|---|---|---|
| 1 | Receive the receipt or vendor bill | Britnie | Email, paper |
| 2 | Rename and file it | Britnie | Google Drive (receipts & bills folder) |
| 3 | Route the vendor bill for review | William | |
| 4 | Create the bill; attach the invoice so Sergey can see what it's for | Britnie | QuickBooks |
| 5 | Find the job and enter the expense | Britnie | Jobber |
| 6 | Review & pay | Sergey | QuickBooks |
| # | Step | Who touches it |
|---|---|---|
| 1 | Receipt or bill lands at a shared email alias, or gets uploaded | Person sends |
| 2 | AI reads it & routes to 1 of 3 paths: already-paid receipt (file only), vendor bill (file + QuickBooks bill), employee reimbursement (file + flag for Zelle) | Automatic |
| 3 | Renamed & filed into the monthly Drive folder the bookkeeper reconciles from | Automatic |
| 4 | Vendor bill created in QuickBooks with the document attached | Automatic |
| 5 | Job suggested from vendor, date & schedule, expense posted for job costing | Automatic |
| 6 | Notification email: done, or flagged for review | Automatic |
| 7 | Weekly payment run | Sergey reviews & pays |
Receipts just need to be sent once, no more double entries, Will doesn't need to approve in the middle of the process, and Jobber stops missing expenses.
QuickBooks Online, Google Drive, Jobber.
"There's a lot of legwork that goes into making sure that we have the right information in the invoice. [...] I spend like the last 45 minutes to an hour on invoicing every day."Britnie Escalante, HR & Admin
Form: Headless automation. Fires when a job closes in Jobber. Britnie reviews a finished draft in QuickBooks instead of building one from scratch.
| # | Step | Who | Software |
|---|---|---|---|
| 1 | Review completed work | Britnie | Jobber |
| 2 | Match against the signed proposal; check for scope changes | Britnie | Jobber, HubSpot |
| 3 | Find the billing or invoicing note; for new clients, confirm the billing contact | Britnie | HubSpot |
| 4 | Create the invoice | Britnie | QuickBooks |
| 5 | Log the invoice number | Britnie | Master timesheet (Sheets) |
| 6 | Trigger the review request | Britnie | GatherUp |
| 7 | Upload to portals where required | Britnie | Client vendor portals |
| # | Step | Who touches it |
|---|---|---|
| 1 | Job marked Closed in Jobber | Automatic trigger |
| 2 | Job matched to its HubSpot record; signed proposal checked against the Jobber description, scope differences flagged | Britnie resolves flags |
| 3 | Draft invoice built in QuickBooks: billing contact, terms, sales rep, service date, description, site address, product category | Automatic |
| 4 | Review & send | Britnie |
| 5 | Invoice number written to the master timesheet | Automatic |
| 6 | GatherUp review request fires on send, except on deposit invoices | Automatic |
| 7 | Client vendor portal upload | Britnie |
Jobber, HubSpot, QuickBooks Online, Google Sheets, GatherUp.
"I actually never close this tab because otherwise I would just reopen it every week and it's easier to just press refresh. [...] This pretty much stays permanently as a minimized tab on my computer."Zander Cohn, Marketing (on the data sources behind the weekly dashboard)
Form: Dashboard & reminders. The numbers pull themselves on a schedule and land in one place, with history.
| # | Step | Who touches it |
|---|---|---|
| 1 | Data pulls on a schedule from every source with an API: QuickBooks, HubSpot, Jobber, Google Sheets, GA4, Search Console, Google Ads & the rest | Automatic. Sources with no API still need manual entry |
| 2 | Calculations run; this period compared against history & against target | Automatic |
| 3 | Saved B2B conversion view, no re-filtering | Automatic |
| 4 | Anything off trend or off target gets flagged | Human reviews the flags |
| 5 | Marketing dashboard & company scoreboard populate | Zander reviews |
| 6 | Sitemap regenerates on publish | Automatic |
| 7 | Finished numbers read & acted on | Sergey interprets & decides |
Connectors may not exist out of the box in ChatGPT for most platforms. Also, a prompt still needs someone to run it.
The team is never behind on reports and data, and no more manual time goes into hunting down data that can be pulled instantly with an API.
Any source with an API (QuickBooks, HubSpot, Jobber, Google Sheets, GA4, Search Console, Semrush, PageSpeed Insights & Google Ads). LinkedIn Ads & SiteDocs stay manual.
"I have to do it on the weekends, which kind of sucks [...] because I have to allocate this two hours on weekends [...] to calculate what's our productivity on jobs."Sergey Kucher, Owner
"If only we can use the time sheet, the master time sheet, I could just have one place to enter the data instead of having to do both [...] it's just like a double task."Britnie Escalante, HR & Admin
Form: Headless automation. Hours sync themselves between Workforce, the master timesheet & Jobber. Techs keep clocking in exactly as they do now.
| # | Step | Who | Software |
|---|---|---|---|
| 1 | Clock in / out | Field techs | QuickBooks Workforce |
| 2 | Pull hours per employee per day | Britnie | QuickBooks Workforce |
| 3 | Enter hours into the master timesheet; split multi-job days by estimated effort | Britnie | Google Sheets (master timesheet) |
| 4 | Find each job and re-enter the same hours | Britnie | Jobber |
| 5 | Chase and fix missed clock-ins | Britnie, Sergey | Workforce, Sheets |
| 6 | Weekend productivity analysis: hours vs. work completed, by project | Sergey | Sheets, Jobber |
The Sheet is doing 3 jobs today: invoice tracking, hour splitting, and productivity analysis.
| # | Step | Who touches it |
|---|---|---|
| 1 | Techs clock in & out | On QuickBooks Workforce |
| 2 | Hours sync to the master timesheet & to Jobber | Automatic |
| 3 | Multi-job days split by revenue | Deterministic. Britnie confirms flagged outliers only |
| 4 | Missing or anomalous entries flagged the same day by email | Britnie follows up |
| 5 | Hours, job costs & backlog assembled before the weekend, outliers flagged | Sergey reviews & decides |
Percent-complete on multi-stage projects stays Sergey's call.
Britnie enters nothing twice, Sergey's weekend analysis becomes a quick review, and missed clock-ins get flagged the next day instead of at the end of the week.
QuickBooks Workforce (API), Jobber (API), Google Sheets (API).
"This is one of the bottlenecks right now, because we do have opportunities. It's not like we're [...] struggling to get business. It's just more of [...] processing them quickly enough and getting them proposals so they can approve it [...] and schedule the projects."Sergey Kucher, Owner
"I joined the company about maybe six months ago [...]. And I still do not know how to price most things [...]."Ed Balta, Project Estimator
Form: Custom application. Real software with its own interface, built on Sergey's existing calculation logic.
| Pro | Pro++ |
|---|---|
| Takeoff sheet upload, pricing logic set up & editable, calc app for the top 3-4 services, proposal generation | Everything in Pro, plus AI-drafted scope descriptions, AI price benchmarking with suggestions, & all services including B2C |
| ~6-8 wks | ~8-10 wks |
Pro covers steps 4, 6, 7 & 9 for the top 3-4 services. The entire new flow is Pro++.
| # | Step | Who touches it |
|---|---|---|
| 1-3 | Pre-research, site visit, visual takeoff | Estimator |
| 4 | Takeoff export ingested; square footage mapped to sizes automatically | Automatic |
| 5 | Scope description drafted from the HubSpot scope of work, routed to the right service rows | Estimator with AI assistance |
| 6 | One tool covering B2B & B2C across all services, on Sergey's existing logic, with required fields prompted before a step can advance | Estimators enter |
| 7 | Estimate moves to review inside the tool, leadership notified it's ready | Automatic |
| 8 | Review of a consistent, pre-validated estimate with flags: price per sq ft against market for property type & size, materials cost benchmark, missing equipment check | Sergey with AI assistance |
| 9 | Proposal generated from the finished estimate | CSR sends |
Square Takeoff, HubSpot, the existing Excel calc sheets & Sergey's formulas, the proposal template.
In jobs won, not hours saved. RayAccess needs to send about $1M of proposals a month across 24-32 proposals, so the average is ~$31K. At a 30% close rate & the 15% margin target, each extra job won is worth ~$4.7K. Pro pays for itself after about 4 extra jobs, roughly 2 more proposals a month for 6 months. Pro++ takes about 5.
"The thing that [...] is the most weekly repetitive all the time thing [...] is the blog post and social media post creation."Zander Cohn, Marketing
"If you can create a structured system [...] I think it's a great idea. It will actually help us to be very consistent with our SEO strategy."Sergey Kucher, Owner
Form: Assistant (Claude skill). Zander drives it himself, step by step. Nothing runs in the background and there's no new platform to adopt.
| Option 1: skill only | Option 2: full build |
|---|---|
| The Claude skill for topics, drafts, Claude Design prompts & social versions. Zander formats & publishes in WordPress himself | Everything in Option 1, plus WordPress integration (formatting, images placed, meta fields) & image generation beyond Claude Design |
| # | Step | Who touches it |
|---|---|---|
| 1 | Topic suggested from recently completed jobs, seasonality & search data | Zander chooses |
| 2 | Photos pulled from the tagged asset library for that job | Zander confirms |
| 3 | Case studies only: draft built from Jobber job notes & photos first, so the interview only fills gaps | Zander interviews staff |
| 4 | Draft written in RayAccess's voice | Zander edits |
| 5 | Claude Design prompt generated for the article & social creative | Zander runs it |
| 6 | Formatted for WordPress with images placed & meta fields filled | Zander reviews & publishes |
| 7 | Social versions generated from the finished post | Zander approves |
Zander saves lots of time, photos stop taking so long to find, and the weekly cadence for SEO is much easier to keep up.
WordPress, the asset library, Jobber job notes (API), Claude.
"So it's (the collections SOP) really intricate. And honestly, we don't do this because it's just nobody has time for it. We have 31, which is horrible. [...] Usually we don't let it get that bad, but it's just a time thing."Britnie Escalante, HR & Admin
Form: Headless automation with email notification. A daily contact list and created QuickBooks tasks.
Daily, the new system will sweep QuickBooks for notes, incorporate the SOPs, and send an email notification to those responsible for collections that includes a daily contact list.
The escalation SOP actually runs, because the system tracks the stage, and Britnie can hand collections to Esmeralda.
QuickBooks (invoices, customers, AR aging, notes), HubSpot, email.
"Somebody's COI, W-9 or agreement is expiring in August. [...] time sensitive, but it's important. [...] It's just hard to have time to go in and look through the things when I have fires to put out."Britnie Escalante, HR & Admin
Form: Dashboard & reminders. An add-on to the same reminder engine as collections.
| # | Step | Who touches it |
|---|---|---|
| 1 | Document uploaded or arrives by email, expiry date read off it | Britnie uploads |
| 2 | Status board per sub & per employee: complete, missing or expired | Automatic |
| 3 | Reminder & request email drafted 30 days before expiry | Britnie sends |
Nothing expires quietly.
Google Drive, email.
"You're going to be my [...] control tower slash diagnostics motherboard."William Brauer, CEO
Form: Dashboard & reminders. A morning brief plus a compliance view. It reads the structured data the other 8 areas create.
Will's stated target is to close 2026 checking this first thing in the morning.
Problems get surfaced daily to leadership instead of discovered.
Jobber, HubSpot, CallRail, Google Calendar (APIs). SiteDocs to verify.
Raised by Sergey. None have been through discovery, so each needs its own session before it gets scoped or priced.
| Area | What was raised |
|---|---|
| AI resume screening | Sergey drops resumes into ChatGPT and asks for a comparison, a score & red flags. They use Indeed plus their own ranking spreadsheet, no ATS. The opportunity is giving AI access to Indeed applicants so screening & scoring happen earlier in the funnel. |
| RFP & legal document extraction | Sergey already uses ChatGPT ad hoc to pull key terms out. Could stand alone, or feed the estimation platform so an RFP goes straight into quoting. |
| EZOffice asset management | Equipment dispatch & return, servicing, vehicle maintenance. Updates get missed, like an oil change on a van that needs recording. Sergey: "we're dropping the ball here." |
Months are relative to kickoff. All durations are approximate.
| Wave | Runs | Duration |
|---|---|---|
| Wave 1 Quick Wins | Month 1 to Month 2 | ~8 wks |
| Wave 2 Core Builds | Month 3 to Month 4 (5 on Pro++) | ~6-10 wks |
| Wave 3 Supporting | Month 5 to Month 6 | ~6-8 wks |
| Wave 4 Long Term | Month 7 onward | Deferred |
Breakdown by problem area.
| # | Area | Build type | Wave | Duration | Investment | ROI |
|---|---|---|---|---|---|---|
| 1 | Receipts & AP | Headless automation | 1 | ~2-3 wks | ~$3.5K | 6 mo |
| 2 | Invoicing | Headless automation | 1 | ~3 wks | ~$4K | 6 mo |
| 3 | Statistical Reports | Dashboard & reminders | 1 | ~3-4 wks | ~$6K | 4 mo |
| 4 | Timesheet & Job Costing | Headless automation | 1 | ~3 wks | ~$5K | 3 mo |
| 5 | AI Estimation Platform | Custom application | 2 | ~6-10 wks | ~$18-23K | 4-5 jobs won |
| 6 | Weekly SEO & Content | Assistant (Claude skill) | 3 | ~1 wk skill only, ~2-3 wks full | ~$1.5K-$4K | 2-3 mo |
| 7 | AR & Collections | Headless automation | 3 | ~2-3 wks | ~$3.5K | N/A |
| 8 | Compliance Document Tracking | Dashboard & reminders | 3 | ~1-2 wks | ~$1.5-3K | N/A |
| 9 | AI Control Tower | Dashboard & reminders | 4 | Scoped after Wave 3 | Scoped after Wave 3 | N/A |