RapidSideKick · Every PC gets a sidekick
RapidSideKick runs quietly on every work computer and keeps an honest record of the day: the apps and windows in front, active time and meetings. RapidPSA holds the tickets, time entries and contracts. RapidCFO holds payroll, vendor bills and what each client pays. RapidDashboard joins all three on person, client and day, so one plain-English question gets an answer that spans every system.
RapidSideKick recordsApps and windows in front, active and idle time, meeting apps, every PC's check-ins
RapidDashboard
The five answers · live
Harbor Point Technology runs managed IT for 81 clients with a service team of 12, every one of them with a sidekick on their PC. Each tab is one question asked of the joined data, with the systems it needed. Move the sliders: every number recalculates in your browser.
Harbor Point TechnologyService team · last 30 daysHow much client work did the team do last month that never made it onto a ticket, and what is it worth?
Hours in the last 30 days. The number on the right is the gap.
Each gap hour is matched to a client, then to that client's contract in RapidPSA.
Each tech closes their own gap: My day hands them the timesheet note, already written. Field techs show laptop time only, so their site visits come from RapidPSA dispatch.
Regrade our flat-fee clients on every hour we spend on them, including time that never reached a ticket.
Margin = monthly fee less hours × loaded cost. Shaded bands are grades C and D.
Pay, taxes, benefits and tools per productive hour, from RapidCFO's payroll model.
The same grades as RapidCFO's client profitability page. This slider also feeds tab 5.
Which of our own software licences are we paying for that nobody opens?
Harbor Point's internal tools. On the right: idle seats and what they cost a year.
Seats to drop at the next renewal.
Is the service desk stretched enough to hire, and does another tech pay for themselves?
Weekly active hours from RapidSideKick. Shaded: the healthy range.
Weekly backlog from RapidPSA.
From RapidCFO's staffing model, with load and backlog filled in from the joined data.
What do our internal meetings cost each month, and which ones produce the work?
Monthly meeting cost divided by the to-dos Remi filed from its minutes.
Loaded cost per hour comes from tab 2.
In each Rapid tool
RapidDashboard joins the record once. After that, each Rapid tool reads the numbers it needs, in the screen people already use.
RapidPSA + RapidSideKick
RapidCFO + RapidSideKick
RapidTablet + RapidSideKick
RapidKiosk + RapidSideKick
RapidDashboard · the hub
Which clients took more recorded hours this quarter than last, and did their fee change?
Any dashboard
Used well
For people who work hard and get interrupted all day, a record they can see is protection. The build follows the sidekick's own four rules.
Each person opens My day and sees their own record before anyone else does.
Dashboards, the wall screen and the briefing show teams. Person-level rows stay with the person and their lead.
RapidSideKick counts keys and clicks per span and keeps no record of what was typed. RapidDashboard reads hours by app, client and day.
Tell the team what is recorded and why: fair client pricing, safe workloads and a clear case for the next hire.
How it's built
One box per company and one line in your RMM. Every PC gets its sidekick the same day, with nothing to do per PC.
Each sidekick's user is matched to their RapidPSA technician and RapidCFO payroll role by work sign-in.
A mapping table turns remote session names, client portal addresses and ticket numbers in window titles into a RapidPSA client. Unmatched time stays internal.
RapidDashboard reads daily totals through the RapidSideKick API and joins them with RapidPSA and RapidCFO on person, client and day.
The daily join, simplified
select person, client, day, sk.client_hours, -- RapidSideKick: recorded time mapped to the client psa.logged_hours, -- RapidPSA: time entries on the client's tickets psa.contract_type, -- RapidPSA: flat fee, block hours or hourly cfo.loaded_cost_per_hour -- RapidCFO: payroll model for the person's role from sidekick_client_day sk join psa_time_day psa using (person, client, day) join cfo_role_cost cfo using (person)
Questions
Which app and window is in front, the web address for work in the browser, active and idle time, and key and click counts per span, never what was typed. Screenshots run only on a schedule the business sets. Each person sees their own day, and managers the business chooses see the team.
On one RapidSideKick server per company. The record leaves only through an API you control, and RapidDashboard reads daily totals through it.
Each pair stands on its own. RapidSideKick with RapidPSA answers unlogged work and dispatch. RapidSideKick with RapidCFO answers idle licences, idle hardware and staffing. All three together grade every client on the hours it really takes.
RapidSideKick records time on the computer. Site visits and phone work come from RapidPSA dispatch and time entries, so the build keeps field roles on logged time and counts only their laptop work as recorded.
A mapping table, set up once: remote session names, client portal addresses, ticket numbers in window titles. Time that matches no client stays internal and shows in the totals as unmatched, so the gap is never overstated.
Harbor Point Technology is fictional, the same sample company as the RapidCFO build. People are shown as roles, clients carry made-up names, and every figure is illustrative.
Fifteen minutes with an AIBMM™ Certified Coach: bring the question you want answered about your team's hours, leave knowing which of your systems RapidDashboard would join to answer it.