Our Work

    Who we work with

    Our client engagements are confidential, so this page tells you who we work with and at what stage, not what we are building for them. That is the same discretion your firm would expect us to apply to your projects.

    What we can show you properly is the capability we have built ourselves, and the discovery work the whole practice rests on.

    Current relationships

    Firms we are working with

    Named with their permission. What we are doing for them stays between us and them.

    Working together

    Sense Engineering

    Engineering consultancy

    In discussion

    Civil-Connect

    Construction management

    If you want to know whether we have solved something like your problem before, ask us on a call. We can talk about the shape of the work without breaching anyone’s confidence, including, later on, yours.

    Built in-house

    Capability we bring with us

    Working embedded means the same problems keep showing up. When one shows up often enough, we build it properly on our own time and bring it with us. Your engagement starts with these already running, and you still own everything we build specifically for you.

    Jurisdictional building code intelligence

    The problem

    North American projects sit under federal, state or provincial and municipal codes all at once. Working out which apply to a given site, and citing them correctly, is manual research repeated on every single project. Firms told us it is one of the easiest places for an error to reach a stamped deliverable.

    What it does

    A code lookup we built ourselves, on our own time, off the back of the same problem showing up in conversation after conversation. It resolves the applicable code stack from a project location and surfaces the referenced standards, with every citation traceable to source so a reviewer can check it. Where jurisdictional lookup is part of your problem, it arrives already working.

    • Federal, state/provincial and municipal layers resolved together rather than searched separately
    • Referenced standards surfaced alongside the codes that invoke them
    • Every citation traceable to its source document, so the reviewer checks rather than trusts

    How we know

    Every problem on this site came from a conversation, not a whiteboard

    Before writing software for this industry we ran documented discovery conversations with more than a hundred engineers, principals, digital leads and operations managers, across 89 architecture, engineering, construction and public infrastructure firms, from two-person consultancies to firms of 35,000. The six problems we work on are the ones that kept recurring.

    100+

    Documented conversations with AE and construction professionals

    89

    Architecture, engineering and construction firms represented

    6

    Recurring problems those conversations converged on

    We’re civil engineers who write software. Meet the team.

    Earlier work

    Before we focused on engineering firms

    We built software for clients in other industries first. It isn’t engineering work and we’re not going to dress it up as though it were, but it is what those clients said about working with us.

    Jonathan Stacey

    Jonathan Stacey

    Co-Founder, GrantFundPro

    Checkout workflow customisation and responsive scaling support

    “VibeOps helped us rapidly implement and customize a scalable checkout workflow within our platform. Their team was extremely responsive, solved several technical integration challenges quickly, and delivered a clean, functional implementation that allowed us to move forward without delays.”

    Steve Lisle

    Steve Lisle

    CEO & Founder, Effortlo

    Automated follow-up system for missed leads

    “VibeOps built an Outlook follow-up system that flags leads I haven’t replied to and reminds me to re-engage. They were extremely professional and incredibly fast on both communication and turnaround.”

    Bring us the problem you have no team for

    Every engagement starts the same way: we scope the real problem in writing before anyone commits to building anything.

    Not sure where you fit? Start with the six problems