Why we don't name our clients

We don't name our clients. Not because we're hiding anything, but because their systems, their data structure, and their internal workflows aren't ours to show off. The same NDA we'd sign to protect your business is one we've already signed for theirs.

How we handle data isolation & security

Every client's systems live in their own isolated environment. We don't reuse a client's specific automation logic, prompts, or data structure for anyone else, not in aggregate, not anonymized, not as a "template" for the next project. What we build for one business stays with that business.

Jump to a story

Industry and outcome at a glance. Pick one and go straight to the detail.

Large National Retailer · BI & Targeted Marketing

Turning a cold call list into a targeted outreach engine

The challenge

During a NetSuite implementation for a large retailer, prospecting for returning customers was still happening cold, the same outreach for someone who'd bought three times last year as someone who'd never purchased at all.

Our approach

We built a dashboard surfacing customer purchasing patterns directly from the new system: when a customer historically buys, how much they typically spend, and how they pay. Instead of a generic call list, sales could prioritize outreach around a customer's actual buying rhythm, reaching people close to when they were likely to purchase again, not months off from it.

The result

Customers reached through the targeted outreach returned at a 50% higher rate than those contacted the old way.

"To be honest, our sales team was drowning in cold lists and flying blind right in the middle of a major system rollout. TriLumen didn't try to sell us some massive, expensive platform. They just took the data we already had and made it actually useful. Our reps finally had a clear target, and the customers we reached through it started coming back way more often."

VP of Sales, National Retail & Distribution

Still running outreach cold instead of targeted?

Small Textile Manufacturer (200 Employees) · Modern Data Stack

Enterprise-grade analytics without the enterprise bill

The challenge

A 200-employee textile manufacturer had outgrown spreadsheets and was trying to get live reporting directly off their operational PostgreSQL database. It wasn't working, running analytical queries against a live transactional system slowed down the actual business software people depended on every day. Looking for a real fix, they'd started pricing out enterprise data platforms, Fivetran, Snowflake, dbt Enterprise, and found the cost and complexity genuinely alarming for a business their size, thousands of dollars a month, and infrastructure that would strain their existing legacy systems rather than work with them. The owner was frustrated and not sure there was a version of this that actually fit their business.

Our approach

We didn't put them on the same stack a much larger company would use. We kept managed PostgreSQL as their transactional database, exactly what it's built for, but separated the analytics layer out entirely so heavy reporting queries never touch the live system again. For transformation, we used DuckDB, which runs in-memory on serverless infrastructure with no standing server cost, paired with dbt to write clean, modular, version-controlled SQL.

Google BigQuery still has a role, but not as the everyday engine. We use it strictly as long-term cold storage, a monthly archive push, so historical data stays searchable and ready for future analysis without paying to keep a massive warehouse running 24/7 for day-to-day reporting.

Because the transformation logic lives in dbt, it's self-documenting. If a new manager joins a year from now, they're not stuck guessing how a metric is calculated, they can open the documentation and see exactly how data moves from PostgreSQL through DuckDB to the dashboard.

The result

A full modern data stack running for roughly $60 to $230 a month, against enterprise-equivalent pricing that would have landed between $1,200 and over $3,000 a month for the same job. Enterprise-grade speed and reliability, at a cost that actually made sense for a 200-person business, with none of the "one developer holds all the knowledge" risk that comes with undocumented custom pipelines.

"Running a 200-person plant means you watch every dollar, and typical enterprise software quotes were giving us sticker shock. TriLumen managed to pull our numbers out of a dozen messy spreadsheets and put them onto one clean dashboard for a fraction of the cost. We finally have a clear picture of our morning numbers without breaking the bank."

Director of Operations, Textile Manufacturing

Overpaying for a data warehouse you don't actually need yet?

Multi-Sheet Ice Arena & Hockey Club · Facility Operations & Yield

Filling every sheet of ice, and getting junior hockey off the whiteboard

The challenge

A three-sheet arena running youth travel hockey from Mites through 18U at A, AA, and AAA, NCDC and USPHL Premier and Elite junior teams, adult hockey, a house league, a figure skating academy, public sessions, lessons, parties, and corporate events, plus a pro shop, concessions, and skate rentals. Ice was scheduled across disconnected spreadsheets, so double-bookings were common and late cancellations left paid-for ice sitting empty. The pro shop didn't sync with the front desk, rental revenue wasn't tracked, and finance spent about a week every month matching registration deposits to the bank by hand. On the junior side, rosters lived on whiteboards, billet family background checks sat in local folders, and every conversation with college and Major Junior scouts was tracked in someone's head.

Our approach

  • One master schedule, with a human on the button. We pulled every sheet into a single scheduler connected to the arena's booking platform. Cancellations outside 72 hours automatically become open ice, and high-margin slots like weekend parties and public sessions are protected first. For the first 30 days nothing published until the scheduling coordinator reviewed it and clicked Approve.
  • Registration that markets itself. Parents register, upload waivers, and set up billing in under two minutes. A family that buys a public skate ticket with kids in the right age range gets a Learn to Skate invite 48 hours later, and party inquiries get a live availability calendar instead of a callback.
  • Recruiting run like a sales pipeline. College coaches and Major Junior scouts became accounts and players moved through stages from first contact to commitment. Coaches log notes by voice from their phones after a game, so nobody has to sit at a laptop, and the locker room whiteboards stayed exactly where they were.
  • A billet portal built for trust. Host families upload background checks, home inspections, and household details to a secure portal, and staff match players by location, allergies, and family dynamics. We walked existing families through exactly who can see their data before asking them to use it.
  • One ledger, proven before it was trusted. Pro shop, rentals, concessions, and online registration now land in one place and reconcile automatically against payment deposits. Finance ran a full month-end close the old way, side by side, until the numbers matched.
  • Yield per sheet, per hour. Ownership sees revenue per hour on each sheet, so a $350 contract rental and a $1,200 public session can be compared honestly, along with pro shop inventory turns tied to the upcoming schedule.

Everything was built and tested over a 90-day offseason, so nothing changed for staff or families during active play.

The result

Ice utilization reached 94%, an 18% gain in sheet efficiency. Lesson re-enrollments rose 32%. Junior program administration dropped 45%, and the club graduated a record advancement class. Month-end close went from seven days to two hours, and the arena saves about $4,200 a month in administrative time, time that went back to coaching, scouting, and families on the ice.

"Managing a three-sheet arena on a bunch of disconnected spreadsheets was a daily headache, and double-booking ice was always a looming fear. TriLumen brought everything together into one master schedule. Our ice utilization jumped to 94 percent, our month-end close went from a full week down to two hours, and my staff can finally focus on the kids on the ice instead of drowning in paperwork."

General Manager, Multi-Sheet Ice Arena

Running a rink or club on spreadsheets and whiteboards?

Enterprise Workforce · Microsoft Copilot Deployment

Rolling out Copilot without exposing what it shouldn't

The challenge

Turning on Copilot for a large, multi-department workforce without first locking down file permissions is how employees end up accidentally seeing executive salaries and confidential data on day one. At enterprise scale, "just-in-time" permissions are almost always messy, and Copilot will surface anything it can technically reach.

Our approach

Before a single license got assigned, we ran a full data governance and permission audit, deploying automated scanners to identify over-shared sites, sensitive executive folders, and outdated financial data, then re-scoping those permissions so the system only ever surfaced what a given user was authorized to see.

Sales and service needed fundamentally different builds. For sales, we deployed Copilot as a bridge between email, chat, and the CRM, so reps stopped manually updating pipeline stages, action items and follow-ups now generate themselves from a single prompt. For customer care, we anchored the assistant strictly to verified internal procedures and ticket history, not the open web, so a complex dispute surfaces the exact, correct resolution script in seconds.

Rolling this out to thousands of users only works if people actually use it. We staged the deployment in cohorts and built a champion network, training power users in every department to build workflow-specific prompts, while standing up a usage dashboard for leadership to track real adoption.

The result

25% → 75%+
Passive usage to monthly active usage

Sales reps stopped manually maintaining CRM records mid-conversation, resolution time on complex customer disputes dropped to seconds, and leadership had a real, measurable view of adoption, not just a license count.

"Rolling out Copilot across the company without a permission audit first is a recipe for disaster. TriLumen came in, mapped out our SharePoint boundaries, and made sure executive folders were locked down tight before a single license went live. They worked closely with our department heads to build real habits, so we ended up with actual daily usage instead of just a bunch of unused licenses."

Head of IT Infrastructure, Enterprise Corporation

Rolling out Copilot without a permission audit first?

County Regulatory Agency · AI-Assisted Records Automation

From 14 days to 45 minutes

The challenge

A mid-sized county regulatory agency was buried under public records requests. The law sets strict response deadlines, but every step was manual: staff opened each email, worked out what the citizen wanted, searched decades of files on old local servers, pulled the matching PDFs, and redacted Social Security numbers, home addresses, and private medical details one click at a time. The backlog ran months, compliance penalties were a real risk, and staff were burned out. Enterprise government platforms were the obvious answer, but their licensing required a multi-year budget approval the agency didn't have time for.

Our approach

Security came first. Government data can't go through public AI tools, so we built inside the agency's existing Microsoft 365 GCC environment, in an isolated, secure instance.

Then we automated the front end. Power Automate pulled requests from the public portal. A secure AI model read each one, categorized it, and searched the internal database for matching records.

We kept humans in charge of the release. Nothing leaves the agency without a human approving it. The AI pre-scans each file, highlights every Social Security number and address, applies a draft redaction layer, and routes the file to a supervisor's queue. Staff open a pre-processed document, verify the redactions in about ten seconds, and click Approve. The system then packages the response and emails the citizen securely.

The result

Average response time dropped from 14 days to 45 minutes, including the supervisor's review. The backlog was cleared within a month. Staff went from twenty minutes of hunting and squinting per request to a ten-second review. The agency had been quoted $240,000 to $370,000 or more by a traditional enterprise vendor. We delivered this for $55,000, on infrastructure they already owned, with ongoing costs of roughly $3,000 a year.

"Our Right-to-Know backlog was completely overwhelming, and our team was spending all day searching and redacting files by hand under tight statutory deadlines. TriLumen built a smart workflow inside our existing Microsoft 365 setup that does the heavy lifting while letting our supervisors keep final control. Dropping our response time from two weeks down to under an hour was a massive relief for the whole office."

Agency Director, County Regulatory Office

Buried under a records-request backlog?

Enterprise Workforce · SharePoint Intranet Overhaul

From a 20-minute search to three seconds

The challenge

At enterprise scale, deep folder structures had become where information went to die. Finding an active HR policy could take twenty minutes, if the version someone found was even still current.

Our approach

We moved the organization away from rigid folder hierarchies entirely, onto a flat architecture powered by structured metadata and a unified corporate taxonomy. We didn't just organize documents, we built a self-cleaning system: when a policy document hits a year old, it's automatically flagged for review and routed to its owner, then archived if it's not reapproved. Nobody sees outdated documentation by accident.

Relevance mattered as much as accuracy. We built audience targeting mapped to role, so a frontline employee logging in sees shift schedules and safety updates, while an executive sees performance metrics and compliance trackers, all from the same root URL. To stop uncontrolled site sprawl, we also built a custom provisioning portal, a manager requesting a new collaboration space fills out a short form, and the system verifies ownership and naming requirements automatically before provisioning it, with zero manual IT intervention.

The result

Search time for critical documents dropped from roughly twenty minutes to seconds, with every employee seeing only current, compliant information, automatically enforced.

"Finding a current policy document used to mean digging through a maze of old shared folders for twenty minutes and crossing your fingers. TriLumen completely cleaned up our structure and set up a system that automatically flags outdated files. Now our team finds what they need in seconds, and we know everyone is finally looking at the right version."

Operations Director, Corporate Enterprise

Drowning in folder chaos and outdated documentation?

Regional Youth Soccer Academy · AI Video, Performance Data & Streaming

Four pitches, 1,200 matches, and nobody on a scaffold

The challenge

A $3.5 million youth soccer academy running 55 boys' and girls' rosters from U9 to U19, with 970 players on four full-size grass and turf pitches. The club hosted 1,200 matches a year across league play, academy dates, and multi-day tournament showcases. Video was costly and slow: operators filmed from elevated scaffolding, staff uploaded recording schedules by hand every time the calendar moved, and coaches spent two and a half hours tagging each match before anyone could learn from it. GPS vests had to be charged, assigned, and downloaded every session. Two to three thousand parents, relatives, and college scouts wanted to watch, and the club wasn't earning anything from it.

Our approach

  • The calendar runs the cameras. We connected the club's league schedules and pitch bookings directly to Spiideo's API, so recordings start and stop on their own whenever the calendar changes. No more CSV uploads. AI AutoFollow tracks the ball and players across all four pitches, which took the scaffolding crews out of the picture entirely.
  • Scoreboards feed the broadcast. Digital scoreboard controllers were wired straight into live graphics. On older analog boards, Spiideo's OCR reads the clock and score from the video itself, so every stream gets accurate score bugs without an operator.
  • Video on the bench, during the match. Low-latency RTSP feeds go from Spiideo CloudLink straight to the bench and into the staff's analysis tools, so coaches can review shape and formations on a tablet while play is still live. Multiple camera angles stay synced, so staff can switch from the wide tactical view to a tight view in one place.
  • The cameras became the tracking system. We pulled Spiideo's tracking coordinates, match events, and heatmaps into the club's own dashboards: team compactness, defensive line width, transitions, and sprints above 24 km/h. The vests went back in the closet.
  • Every clip lands where it's useful. At the final whistle, tagged clips are filed to each player's development plan and to scout-facing recruiting dashboards automatically. AI highlights of goals and red cards reach the club's social feeds within 60 seconds.
  • Turning viewers into revenue. Live feeds were routed into a paywalled streaming service, so families and scouts buy access to league matches and tournaments. The stream itself carries sponsor score bugs, half-time watermarks, and overlays.

The result

$82,000 in pay-per-view revenue across the 1,200-match calendar, plus $19,000 in new sponsor inventory that didn't exist before. $28,000 a season saved on videographers, 16 hours a week of scheduling admin gone, and two and a half hours of manual tagging per match cut to zero. Social impressions rose 412%. Coaches got live video on the bench and thousands of data points per match, without a single vest to charge.

"We run 55 teams across four pitches and we were spending hours on manual video recording and tagging. TriLumen hooked our match schedules straight into automated cameras so everything runs on its own. Our coaches get live video right on the bench, parents can tune in from home, and we even built a new revenue stream out of the live streams."

Club Director, Youth Soccer Academy

Filming every match but not earning from it?

Large National Retailer · ERP, WMS & Delivery Migration

When two systems stopped agreeing with each other

The challenge

A large national retailer migrating off legacy systems onto NetSuite, alongside a new warehouse management system and a last-mile delivery platform, all at once. The biggest issue wasn't any single system, it was the lag between them. An action in the warehouse system needed to reflect in NetSuite, and vice versa, and the volume of real-time data flowing between the two proved heavier than either system could sustain at launch.

Our approach

We stepped back to hourly reconciliation while we solved it properly, a combination of scaling system capacity and reducing the volume of data moving through each sync. That workaround ran for two weeks. We didn't move back to real-time until we were completely certain the fix would hold.

That lag touched inventory accuracy, delivery scheduling, and the selling cycle while it was live. We'd recommended shifting go-live to a slower period to protect the customer experience during the transition. Leadership held the original date. We managed the impact as carefully as we could, but there were real failed deliveries and real customers affected during that window. We don't pretend otherwise.

What we controlled was the response. We stood up twice-daily calls, sales, customer care, and operations, open to any leadership who wanted in, and built daily microlearning modules for every leader involved, started before go-live and continued through the full resolution.

The result

A fully resolved real-time sync within two weeks, an organization that stayed informed and trained throughout, and a hard lesson in what happens when a go-live date gets prioritized over a system's real capacity.

"Migrating our warehouse management and NetSuite systems simultaneously was a heavy lift, and our data sync was lagging right out of the gate. TriLumen didn't duck for cover when things got bumpy. They stepped in with a practical fix, kept leadership completely in the loop with daily check-ins, and got our real-time sync locked down solid within two weeks."

Chief Operating Officer, National Retailer

Facing a system migration with a tight go-live date?

Mid-Size Manufacturer · Equipment Maintenance Automation

Turning a broken machine into a self-routing ticket

The challenge

On a manufacturing floor, every minute a critical machine sits broken destroys margin. A manual process, clipboards, phone calls, emails to a maintenance team, is too slow to catch that bleeding before it adds up.

Our approach

We replaced the paper trail with a three-button mobile form. An operator taps the machine ID, selects the issue type, photographs the fault, and submits. From there, a single automated flow branches three ways at once: an instant, photo-attached alert to the maintenance team, an automatic flag in the production schedule so a broken machine can't be accidentally assigned new work, and a live inventory check for the failed part.

Equipment downtime automation flow An operator submits a form, triggering an automated flow that branches into three parallel actions: a maintenance alert, an asset lookup, and an inventory check. Operator submits form Automated flow triggers Maintenance alert Sent to Teams channel Asset lookup Flags machine as down Inventory check Orders part if needed

If the part isn't in stock, the system doesn't wait on a human to notice. It drafts a purchase request automatically. Below a set cost threshold, it approves and submits the order itself. Above that threshold, it escalates to the plant manager with the machine's downtime cost per hour shown right next to the part cost, approvable from a phone notification.

Inventory and escalation flow Continuing from the inventory check: if the part is in stock, a pick ticket is generated. If not, a purchase request is drafted and automatically approved under 1500 dollars, or escalated to the plant manager above that threshold, before the purchase order is released. Inventory check Part in stock Pick ticket generated Part not in stock Draft PO created Under $1,500 Auto-approved Over $1,500 Needs approval PO released

When the technician closes the ticket, the system calculates the full downtime duration automatically and logs it, feeding a live dashboard tracking mean time to repair, monthly cost of downtime, and which equipment fails most often.

The result

45 min → under 30 sec
Time to report a fault

What used to depend on someone finding the right person to call became a self-routing system, alerting the right team, protecting the schedule, and even purchasing its own replacement parts within a set budget, all without a single manual handoff.

"When a critical machine went down on the plant floor, our old process relied on clipboards, phone calls, and shouting across the room. TriLumen built a simple mobile form for our operators. Now a broken machine instantly alerts the maintenance team, flags our production schedule, and can even auto-purchase replacement parts under a set budget, saving us hours of painful downtime."

Plant Manager, Mid-Size Manufacturing Facility

Manual downtime tracking eating into your margins?

Regional Food Distributor · 75 Delivery Vans · Routing & Telematics

From spreadsheet dispatch to 98% on-time

The challenge

A regional commercial food distributor running 75 delivery routes across three states was losing margin on fuel and missing delivery windows. Dispatchers built every route by hand in spreadsheets each afternoon, with no view of live traffic, driver break compliance, or dock delays. When a truck hit traffic, the customer didn't hear about it until the window had already closed, and loads got rejected at the door.

Our approach

  • We kept the hardware they already owned. No enterprise logistics suite and no new devices for drivers. We built a middle layer on Python and Google Cloud Functions on top of their existing telematics.
  • Routes re-sequence themselves. As morning traffic changes, the system reorders the stops and pushes updated navigation straight to the drivers' existing tablets.
  • Customers hear first. When a truck's ETA slips more than 15 minutes, the receiving restaurant gets a text with a live tracking link automatically. No dispatcher has to make the call.
  • Dispatch by exception. Dispatchers stopped babysitting the routes that were running fine. They start the day with one dashboard showing only the handful of routes that need a human.

The result

82% → 98.4%
On-time delivery rate
$142,000
Annual fuel savings
4 hours
Reclaimed by dispatch every morning

Routes adjust themselves, customers are warned before a window is missed, and dispatchers spend their mornings on exceptions instead of spreadsheets.

"Before this, our dispatchers were essentially professional firefighters. They spent half their morning staring at spreadsheets trying to guess where traffic was going to break us. Now, the system handles the routing, our customers get a text with a live map before they even have to call us, and our team only looks at exceptions. It completely changed how our trucks run."

Director of Operations, Regional Commercial Distributor

Still building routes in a spreadsheet?

B2B Marketing & Consulting Agency · 45 Staff · Scope, Capacity & WIP

Catching scope creep before it eats the margin

The challenge

A growing 45-person agency was losing margin it couldn't see. Account managers gave away extra scope to keep clients happy, creative directors were booked at 140% while junior copywriters sat underused, and finance didn't find out a project was underwater until 30 days after month-end close.

Our approach

  • A scope alarm at 85%. When logged hours on a deliverable hit 85% of budget before final review, the account director is notified and a draft change order for the client is ready to send.
  • Capacity four weeks out. A weekly forecast shows staffing gaps a month ahead, so leadership books freelancers early instead of burning out the senior team.
  • WIP that posts every day. Work-in-progress revenue is calculated and pushed to the ledger daily, so project health is visible while there's still time to act.
  • Clear lines between systems. Project management owns the work, accounting owns the money, and the rules between them are enforced automatically.

The result

78% less
Unbilled scope leakage
81%
Sustainable average utilization
5 days → 1 afternoon
Month-end financial reporting

Scope problems surface while they can still be billed, staffing is planned before it's a crisis, and margins are predictable month to month.

"We used to find out a project went underwater three weeks after the client paid the final invoice. It was a massive blind spot. Having a system that taps us on the shoulder when a scope hits 85%, and drafts the change order automatically, has stopped the bleeding. Our margins are actually predictable now."

Managing Partner, B2B Marketing & Consulting Agency

Finding out about overruns after the invoice is paid?

Multi-Location Dental Group · 6 Clinics, 14 Dentists · Patient Recall

Filling empty hygiene chairs without adding front-desk work

The challenge

A six-clinic dental group with 14 dentists had a major leak in its hygiene recall pipeline. More than 1,200 patients were overdue for their six-month cleanings, but the front desk was too busy answering inbound calls to work the outbound recall lists. Meanwhile, last-minute cancellations left expensive chair time sitting empty.

Our approach

  • Built on the system they already ran. We connected directly to the group's existing practice management software. No new platform for staff to learn.
  • Recall by text, not postcard. Patients get a personal text sequence six months after their last visit, with a self-serve booking link tied to live chair availability.
  • Cancellations fill themselves. When a patient cancels within 48 hours, the top ten waitlisted patients whose appointment type fits the slot get a text. The first to reply yes gets the chair.
  • The front desk gets its time back. Routine booking runs on its own, so front-desk staff focus on patients in the office and on complex treatment plans.

The result

41% → 76%
Hygiene recall compliance in 90 days
$310,000+
Preventive care revenue recovered
89%
Last-minute cancellations refilled automatically

Overdue patients come back on their own, cancelled chairs get refilled without a phone call, and the front desk spends its day with the patients in front of them.

"Our front desk was drowning in phone trees and manual recall lists while our hygiene chairs sat empty. TriLumen didn't try to sell us some bloated hospital software; they plugged right into what we already ran. Our recall compliance jumped to 76% in three months, and our staff can finally focus on patients standing right in front of them instead of being glued to a phone."

Practice Group Administrator, Multi-Location Dental Group

Hygiene chairs sitting empty?

Independent Restaurant & Bar · 92 Seats · Prime Cost Reporting

From a shoebox of invoices to a 6 AM briefing

The challenge

A busy neighborhood restaurant and bar was winning on the floor and losing in the back office. Toast ran the POS, 7shifts ran the schedule, MarginEdge held the invoices, and QuickBooks kept the books, but none of them talked to each other. Labor and food cost, the two biggest lines, only showed up when the P&L landed three weeks after the month closed. Vendor invoices sat in the office until Sunday night, so a 14% jump in seafood went unnoticed until food cost was already blown. Monday and Tuesday lunches were staffed like weekends, and tip-outs and cash reconciliation ate hours after close.

Our approach

  • We kept every system they already ran. No new POS and no new app for staff. Setup happened around service, so nothing changed on the floor or in the kitchen while we built.
  • Invoices code themselves overnight. Vendor invoices are captured, coded, and posted to QuickBooks automatically, and every price change is flagged against the recipes it touches.
  • Prime cost every morning, by daypart. Yesterday's labor and food cost land against target on the owner's phone at 6 AM, so the GM fixes a Tuesday staffing leak on Wednesday instead of next month.
  • Tip-outs in one tap. Calculated from POS sales and the schedule, matched to card tips, and released only when a manager approves.

The result

3.8 points
Prime cost reduction in the first 60 days
0 hours
Sunday-night invoice entry
Under 10 min
Daily briefing review for the GM

The owner knows the numbers before the door unlocks, menu prices move when ingredient prices do, and the team spends its time on guests instead of spreadsheets.

"We used to find out we had a bad month after the month was already over. Now we know our numbers before we unlock the front door, and the team can actually focus on the guests instead of spreadsheets."

General Manager, independent restaurant

Finding out about prime cost three weeks too late?

Independent Retail & Cafe · Coffee Bar + Gift Boutique

One shop, two businesses, and finally one set of numbers

The challenge

A neighborhood corner shop pairing a specialty coffee bar with a curated gift boutique had steady foot traffic and a loyal morning crowd. Behind the counter, it was two businesses that didn't talk to each other. The coffee bar ran on Square, while boutique inventory lived in a separate spreadsheet, so month-end stock counts turned into a weekend-long, error-prone marathon. The owners knew lattes sold fast, but couldn't tell whether the ceramics and seasonal cards were earning their shelf space once packaging and shipping were counted. Afternoon lulls were staffed on gut feel, and gift items were reordered when a shelf looked empty, which meant too much of the slow sellers and not enough of the favorites before a busy weekend.

Our approach

  • We kept the shop the way the owners built it. No corporate ERP and no new screens at the counter. We built a light data stack behind the scenes that connects the POS, inventory, and the books.
  • Coffee and retail, split every morning. A 7 AM briefing on the owner's phone shows yesterday's cafe and boutique sales side by side, measured against labor by daypart, so shifts get trimmed where the numbers say to trim them.
  • Reorders driven by sales, not empty shelves. Low-stock alerts fire automatically for fast-moving gift items and coffee beans alike, and slow sellers are flagged early, before they sit on a shelf for months.
  • Bookkeeping that happens overnight. Daily sales, tips, and vendor payouts post to QuickBooks automatically, so nobody reconciles two spreadsheets on Sunday night.

The result

24% less
Excess inventory holding cost
0 hours
Sunday-night sales reconciliation
Under 5 min
Daily margin check for the owner

The owners can see exactly what the cafe contributes versus the boutique, and seasonal buying now follows the numbers instead of a hunch.

"We opened the shop because we love coffee and beautiful things, not because we love data entry. TriLumen got our systems talking to each other so we can actually look at our numbers over coffee instead of stressing over a spreadsheet after close."

Co-Owner, Neighborhood Coffee & Gift Boutique

Running two businesses under one roof?

Independent Engagement · Small Business Systems Integration

Making QuickBooks and HubSpot actually agree

The challenge

Sales and accounting systems that don't agree with each other create duplicate customers, mismatched revenue, and invoices nobody fully trusts.

Our approach

  • We started with the human problem, not the API. Before any technical work happened, we defined a clear boundary: HubSpot owns the pipeline, QuickBooks owns the money. Sales reps can trigger an invoice request from HubSpot, but they can never touch a financial record or tax setting directly.
  • Deduplication had to be strict, not cosmetic. We never relied on company name matching alone. A verified email domain or tax ID became the real unique identifier, so "Acme LLC" and "Acme Incorporated" didn't quietly become two different customers with a fractured history.
  • We synced line items, not just "Closed-Won." When a deal closed, we mapped the actual SKU-level line items to the right accounting category, applied the correct tax code by shipping address, and generated a draft invoice, not just a status flag someone had to interpret.
  • Automation breaks. We planned for that, not around it. If an API limit was hit or a required field was left blank, the system didn't fail silently. It sent a direct alert to whoever needed to fix it, with a link straight to the record.

The result

10 hrs/week → 0 hours
Re-key between QuickBooks and HubSpot

An integration that runs without silent failures, duplicate customers, or a bookkeeper reconciling invoices by hand every month.

"Our sales team was living in HubSpot while our bookkeeper was working in QuickBooks, and the two systems constantly argued with each other over names and invoices. TriLumen set up a clean boundary where HubSpot owns the pipeline and QuickBooks owns the money, and it actually stays synced. We went from ten hours a week of manual data re-keying down to zero."

Managing Director, Professional Services Firm

Tired of your systems arguing with each other?

Before we signed on, I wanted proof that these guys understood real-world mess, not just textbook theory. Reading how they untangled another owner's inventory nightmare gave me the confidence that they wouldn't just sell us software we'd end up hating.

CEO, mid-market manufacturing firm

Have a problem that looks like one of these?

Book a call