WHAT WE DO

Modernization, cloud, AI, software, or talent - pick the one that is costing you now. Sector practices and client engagements are further down this page.

ALSO ON THIS PATH

BY INDUSTRY

Every industry has its own 1995

Legacy wears different uniforms. These are the patterns we see by sector - and the solution or product plays that fit. ERP industry editions live under Products.

Manufacturing

We modernize the software between the order and the shipped pallet: aging MES and ERP, machine data stuck on the floor, planning done in spreadsheets. Connect shop-floor reality to business systems, and automate the paperwork in between.

FAQ

Manufacturing FAQs

Can you work with our OT/IT separation?

Yes - we design for it: read-only data diodes from OT where required, no cloud dependency on the line, and security reviews with your OT team before anything touches a PLC network.

Our ERP is heavily customized. Is that a problem?

It's the normal case. The assessment maps which customizations encode real differentiation (kept, documented) versus historical accidents (retired) - before any migration decision is made.

Healthcare

We modernize the operational and clinical-adjacent systems healthcare actually runs on - scheduling, stores, billing, lab integrations - with privacy built into the architecture, not bolted on as a policy PDF.

FAQ

Healthcare FAQs

How do you handle PHI during development?

Masked or synthetic data by default; when production data is unavoidable it stays in your environment under your controls, with access logged. Our staff never take copies - architecture makes that the easy path, contracts make it the only one.

HIPAA / regional compliance - whose rules apply?

Your regulator's. We implement HIPAA-class controls as engineering (encryption, access, audit) and map them to your specific regime with your compliance officer in the loop from the sprint.

Logistics & Distribution

From AS/400 warehouse systems to paper PODs, logistics carries more legacy per revenue dollar than almost any sector. We modernize the software that moves goods while trucks still leave the yard.

FAQ

Logistics & Distribution FAQs

Peak season is coming - when can work safely start?

Assessment and characterization work is read-only and can start anytime. Cutovers are scheduled outside your peak windows by design, and every migration has a rehearsed rollback.

Financial Services

Banks, insurers, and lenders run correct-but-calcified cores surrounded by decades of workarounds. We modernize around the ledger with reconciliation-grade discipline - and put AI into workflows under the governance your regulator expects.

FAQ

Financial Services FAQs

Can your AI systems pass model-risk / audit review?

They're designed for it: retrieval-grounded outputs with citations, policy checks before actions, human approval where consequences warrant, immutable logs, and documented evaluation. We build the evidence pack alongside the system, not after it.

Retail & E-commerce

Retail often sells at internet pace while the back office still runs last decade's batch. We modernize inventory, order, and fulfillment so operations keep up with the merchandising calendar.

COMMON PAINS

  • →Inventory truth differs by channel, warehouse, and day of week
  • →Promotions break the order pipeline in new and seasonal ways
  • →The ERP thinks in purchase orders; the business thinks in drops
  • →Customer data is everywhere, therefore nowhere

PLAYS

FAQ

Retail & E-commerce FAQs

Can you work around our peak freeze?

Freezes are healthy. Discovery, build, and parallel-run all proceed during freeze; only cutovers wait. A well-run program treats your calendar as a design constraint, not an obstacle.

Education & Training

Institutions run on admissions spreadsheets, fee registers, and heroic administrators. We modernize the operations layer and bring grounded AI to student-facing workflows - with the data care education demands.

COMMON PAINS

  • →Admissions season is a spreadsheet marathon with occasional data loss
  • →Fee collection status depends on who you ask
  • →Student queries repeat endlessly; staff answer instead of teaching
  • →Reporting to boards/regulators is a quarterly scramble

PLAYS

FAQ

Education & Training FAQs

How do you handle student data?

Minimum-necessary access, masked development data, and clear residency - plus assistant designs that answer from policy documents rather than student records unless explicitly scoped and approved.

Construction & Fit-out

Construction money moves through BOQs, variation orders, certified claims, retainage, and pay apps. We put that commercial loop in software - Gulf fit-out in two languages, US specialty draws on AIA forms, A/E studios without a Deltek program.

FAQ

Construction & Fit-out FAQs

One product for GCs and subs?

No. Bunyan is Gulf fit-out commercial ops. Drawflow is US specialty-sub draws and waivers. StudioLedger is A/E project accounting. Pick the job, not a generic 'construction suite.'

Does AI certify a claim or pay app?

No. It extracts, drafts, and flags. Certification, GC approval, and export stay human.

Real Estate & Property

Residential blocks and scattered-site portfolios run on statutory clocks and maintenance inboxes. We make service-charge recoverability and work-order triage first-class - not year-end surprises and overnight voicemail.

COMMON PAINS

  • →Section 20B's 18-month clock is discovered when the cost is no longer recoverable
  • →Year-end service-charge packs are a war room, then an accountant argument
  • →The maintenance inbox treats a gas smell and a dripping tap as the same ticket
  • →Vendor dispatch happens in email; NTE and owner approval are folklore

FAQ

Real Estate & Property FAQs

Commercial property?

Chargebook is UK residential block / RTM service charge. Fixflow is mid-size residential and scattered-site PMs. Commercial facilities and investment-management stacks are a different conversation.

Does Fixflow replace AppFolio or Yardi?

No. It is the maintenance desk beside the PMS - intake, triage, WOs, vendors.

Energy & Utilities

Renewable developers, solar O&M, and oilfield or utility contractors share a pattern: the work is in the field, the money is in a packet, and the clock is someone else's. We make interconnection packages, alarm triage, and ticket-to-cash explicit.

FAQ

Energy & Utilities FAQs

Does Gridpath file at the ISO?

No. It prepares and QAs the package. Your engineers file. It will not auto-stamp NERC-compliant.

Will Suntriage auto-dispatch?

No. Classification is conservative. A NOC human disposes; then a work order can go out.

Professional Services

Agencies, consultancies, and design studios leak margin in two places: work that was never on the SOW, and time that was never billed. We watch the baseline and keep project accounting honest.

COMMON PAINS

  • →Scope creep arrives as a Slack message that felt like partnership
  • →Harvest is full; invoices are not
  • →Change orders are Word docs the client never signs
  • →A/E studios need phase billing and proposals without buying Deltek

FAQ

Professional Services FAQs

Product companies without SOWs?

Scopeguard needs a signed baseline. If there is no SOW, there is nothing to watch - start with Flow or a written scope, not a sentinel.

Does AI send the change order?

It drafts. You send. The client decides on a public link you control.

Food & Beverage

SMB food processors do not have two years for a custom MES. They have FSMA 204, HACCP, mock recalls, and an investigator who wants a sortable file this week.

COMMON PAINS

  • →Lot genealogy is a binder and a shift lead's memory
  • →CCP checks are paper that gets photographed after the fact
  • →A mock recall takes a war room and still misses a customer lot
  • →Supplier documents are emailed PDFs with no chase

FAQ

Food & Beverage FAQs

Is this a full MES?

No. Tracebox is FSMA 204 traceability, HACCP, and recall readiness for SMB processors - not a custom MES rewrite.

Who uses it on the line?

Operators on a PIN kiosk; QA on deviations and recalls; auditors on a tokenized portal.

Veterinary

Companion-animal clinics miss calls at lunch, overnight, and whenever the desk is rooming a patient. Those calls are appointments that went down the road. We answer, book, and recover - without giving medical advice.

COMMON PAINS

  • →After-hours and lunch-break calls go to voicemail, then to a competitor
  • →The desk cannot book while restraining a patient
  • →Recalls, refills, and estimate follow-ups depend on whoever remembers
  • →An unguarded chatbot inventing medical advice is a board complaint

FAQ

Veterinary FAQs

Is this human healthcare?

No. Companion-animal veterinary clinics. Human behavioral-health credentialing is Credenza; contact-center Voice is the platform underneath when you need the full telephony OS.

Does it diagnose?

No. Guardrails block medical advice and toxicity questions. The product books, recovers, and follows up.

Wholesale Distribution

Wholesale order entry is still people re-typing customer POs into the ERP. The catalog knows the SKU; the PO does not. We extract, match, and send humans only the exceptions.

COMMON PAINS

  • →POs arrive as PDF, Excel, photo, and fax
  • →Customer part numbers are not your SKUs
  • →CSRs re-type lines and still miss UOM conversions
  • →The ERP sees garbage because nobody wants to look slow by asking the customer

FAQ

Wholesale Distribution FAQs

Is this DTC e-commerce?

No. The buyer is a wholesale distributor taking customer POs into an ERP - industrial supply, electrical, plumbing, HVAC, MRO.

Will it invent SKUs?

Low-confidence lines go to a CSR. That is the product, not a failure mode.

HOW WE WORK WITH CLIENTS

Proof from production

How we've run modernization and AP automation in production - the problem, the approach, and where it landed.

Logistics & distribution

Mainframe exit with the warehouse still shipping

Moved a COBOL warehouse and billing system onto a modern platform with strangler-fig seams and parallel runs - no big-bang weekend - while fulfillment kept its cutoffs.

THE PROBLEM

  • Warehouse management and billing still ran on COBOL, on hardware held together by a thin support contract, owned by two engineers close to retirement.
  • Every change sat in a request queue. The batch window set cutoff times customers no longer accepted.
  • Docs had drifted so far that the only trustworthy spec was the running system.

WHAT WE DID

  • Two-week assessment: COBOL analysis to recover business rules, dependency maps, and a risk-ranked module list.
  • Characterization tests first: golden masters that pin current behavior - including the quirks the business still relies on - before any code moves.
  • Strangler-fig: pull billing out behind a stable interface; run old and new in parallel with nightly reconciliation until the numbers match for a full cycle.
  • Capture knowledge from the retiring engineers into docs and tests while they can still confirm intent.

THE RESULT

  • Billing runs on the modern platform; the mainframe module is retired. Cutover happened when reconciliation stayed green, not because a calendar said so.
  • Batch-window limits gone for migrated work; changes ship in sprints instead of quarterly change requests.
  • Key-person risk turned into documented, tested code the team can own.

TOOLS WE USED

COBOL analysis toolingTypeScript/Node servicesPostgreSQLKafka-class eventsParallel-run reconciliation harness

Manufacturing - finance operations

The AP inbox that reads itself

AP document intelligence: extract invoices, check them against POs, post the clean ones to the ERP, and send the messy ones to people - with an audit trail on every action.

THE PROBLEM

  • Thousands of supplier invoices a month as PDFs, scans, and phone photos, typed into an ERP by hand.
  • Three-way matching (invoice ↔ PO ↔ receipt) done by eye, so problems showed up weeks late - usually as an angry supplier call.
  • Month-end ran longer than it should, and nobody could say exactly why.

WHAT WE DID

  • Test on a real month of invoices before committing to anything.
  • Extract with layout awareness, then validate totals, tax, and PO references. Failures get scored and routed - they never post quietly.
  • High-confidence invoices go straight through. Ambiguous ones land in a review queue with the evidence highlighted.
  • Posting agent runs under policy (amount limits, supplier allowlists) with an audit log and human approval above thresholds.

THE RESULT

  • Most invoice volume posts without a human touch; the rest get a clear review queue.
  • Exceptions show up at ingest, not at month-end.
  • Finance can answer who posted what and why in seconds.

TOOLS WE USED

Document AI extractionRule-based validationAgent Cloud governanceERP integrationReviewer queue UI

HOW AN ENGAGEMENT ACTUALLY RUNS

Including the part that went long

3 weeks

from kickoff to a costed, sequenced plan

A plan you could execute without us. Most clients do not - but the leverage is yours either way.

week 11

client engineers changing extracted services unsupervised

Pairing and documentation from day one, so ownership transfers as the work happens rather than at the end.

We were off that project in month 8. Sustained dependency is a business model, not an outcome.

7 → 9

months estimated, then actually taken

The slip was data reconciliation - harder and slower than the code extraction it supported.

We publish this because a partner who has never overrun has either never done the work or is not telling you. We budget reconciliation differently now.

FIGURES FROM A SINGLE ENGAGEMENT AND FROM WORK ACROSS CLIENTS - EACH MEASURED AS DESCRIBED