Quiet intelligence for complex systems.

Fi Systems is a Canadian software studio. We build AI tools that let engineering and operations teams stop retyping and chasing information from one tool to the next.

Read information out of drawings, documents and records.

Example views
Base plate · 1 Upright · 2 Bearing housing · 2 Shaft · 1 Hex bolt · 8

Found on sheet 1 of 1

  • Base plate× 1
  • Upright bracket× 2
  • Bearing housing× 2
  • Shaft× 1
  • Hex bolt M16× 8

5 parts · 14 units · ready to check

Built for Bronswerk Makers of Qarrot

Most of the work happens between systems.

Technical companies run on drawings, documents, spreadsheets and systems that don't talk to each other. People fill the gaps by retyping, checking and emailing, and every handoff is a chance for something to go wrong. Three places it happens:

Engineering knows what a project needs. Getting it ordered means copying it all over again.

  1. The design
    parts_list.xlsx

    Engineering's list of parts, straight from the design software.

  2. Copied by hand
    FA-2041-032
    FA-2O41-051
    HW-0816-0608

    Retyped into a spreadsheet. One part number has the letter O instead of a zero.

  3. Questions by email
    Is this a new part, or do we already have it?

    Someone has to go and check.

  4. Order on hold
    Purchase orderWaiting for answers

    Nothing gets ordered until every line is sorted out.

The same gaps show up across the operation

We apply the same capabilities wherever work passes from one team or tool to another.

  • Procurement

    Parts lists go straight from the design files to purchasing, with every part checked against what you stock.

  • Quality and compliance

    We tie inspections, certificates and audit records back to the drawings and specifications they're meant to prove.

  • Maintenance

    Repair history and technician notes become an early warning for the problems that keep coming back.

  • Engineering

    We read drawings and specifications, and build the calculation and checking tools engineers repeat every day.

  • Operations

    We move approvals, handoffs and records out of inboxes and into one place every team can see.

How we work

Four steps, and where we've already done each one.

  1. 1

    Start with one real process

    Every project starts with the work itself: who does it, what they use, and where it slows down. We pick the part where software will make the biggest difference, and begin there.

    Bronswerk

    We started with the handoff that slowed their projects most: getting parts from the drawing to purchasing.

  2. 2

    Show it early, shape it together

    We put something working in front of the people who'll use it as soon as we can. What they notice in their real work shapes what gets built, long before anything is final.

    Bronswerk

    Their engineers and buyers tested each version on real projects. What they flagged changed the rules, the wording and the flow.

  3. 3

    Fit into what you already run

    We connect to your ERPs, databases and older software that still does its job, and build around them instead of asking you to start over.

    Bronswerk

    Their parts came from several generations of equipment and numbering. The tool works with that history instead of forcing a cleanup first.

  4. 4

    Stay with it after launch

    Launch is where real use begins. We host, support and keep improving what we build as your work changes.

    Qarrot

    Our own employee recognition platform, which we've built and run for years for companies around the world.

See what we've built

Led by its founders

They shape each project with the client and bring together the people it needs.

  • Aaron CarrChief Executive Officer
  • Ulises OrtegaChief Technology Officer
About us

Have work stuck between systems?

A few lines about the work is enough to start.

Tell us about your challenge