Custom software · Bay of Fundy

Intake to ship, for operators who already know their work.

Fundy Ops Studio is a small Atlantic shop. We build the interfaces, APIs, and intake paths that clinics, integrators, and municipal teams actually use — then we stay for the middle: the change request, the handoff note, the next release.

Start a conversation How a job moves →

Services

The work we like, written plainly.

We are not a staff-aug bench and we are not a pitch-deck factory. If the job is a brochure, we will say so. If the job is an operator tool that has to survive next Tuesday, we are in range.

  • Custom operator UIs

    Screens for people who already have a process: intake desks, interface queues, survey close-out, workboards. Readable type, honest empty states, no stock photography required.

  • APIs that match the real path

    Resources named after the work, not after a framework tutorial. Status, jobs, contacts, the boring verbs. Documented enough that a teammate can pick it up in a week.

  • Intake → ship

    A form that becomes a ticket, a ticket that becomes a build, a build that has a ship note. We would rather improve that spine than invent a fourth methodology.

  • Integration-minded builds

    We sit comfortably next to HL7 engines, Genetec-class platforms, and the systems Atlantic operators already bought. The UI is not allowed to pretend those systems do not exist.

Approach

One job, four marks in the notebook.

  1. Hear the operator

    We write down the path as it is walked today, including the spreadsheet that everyone pretends is temporary. The first artefact is a short brief, not a colour palette.

  2. Shape the smallest useful slice

    A form, a list, an API method, a handoff page. We ship that slice while the rest of the map is still in pencil. Scope is a kindness.

  3. Build in the open with the team

    Issues, a workboard, and notes a Grok Bot thread can continue. The marketing site is allowed to be pretty; the job record is not allowed to be cute.

  4. Ship, then leave a trail

    Changelog, owner, and the next obvious follow-up. If we disappear for a fortnight, the next person should not have to reverse-engineer our taste.

Contact

Tell us the job, not the stack.

This form stays in the browser for now — the next Fundy build is to post it to GitHub Issues. No need for a procurement novel. A paragraph and a deadline is enough to start.

Fundy Ops Studio

14 Front Street
Saint John, New Brunswick E2L 1A1

hello@fundyops.studio
506 555 0194