Christopher Folmar, Engineering Manager at Fullscript.
/chris · ottawa, on · 2025
Engineering manager at Fullscript

I help engineering teams achieve more, and the engineers doing the work grow.

I'm Chris Folmar. I run three engineering teams at Fullscript, modernize the systems behind the business, and put most of my AI energy on the boring problems — so people can get back to the work that actually needs their judgment.

A note

I've always been drawn to the space between the work people are trying to do and the systems that either help them or get in their way.

The work I care about usually starts with a simple question: Why does this feel harder than it needs to?

My career has grown from hands-on technical work into engineering leadership, but I still feel most connected to the work when I'm close enough to understand the real friction. Where are people losing time? Where is ownership unclear? Where are teams relying on memory, follow-up, or manual effort? Where could better tooling or clearer communication make the day feel less chaotic?

I like practical systems. The kind that reduce noise. The kind that help teams move. The kind that make someone's job a little less frustrating.

I'm trying to build a career and a body of work around that idea: useful systems, thoughtful leadership, strong execution, and a bias toward leaving things clearer than I found them.

Chris Folmar
Impact at a glance

A few proof points from the last few years of scaling teams, rebuilding business systems, and shipping AI-enabled workflows.

40%+
AI-driven operational time saved across 5 depts
43%
NetSuite transaction reduction
95%
Invoicing ownership migration
300%+
Project throughput increase
<1%
MR rollback rate
AI Transformation · Team GSD

Most AI projects fail because the operating model around them is wrong. My work with Team GSD at Fullscript shows how to get it right.

Team GSD takes the work people shouldn't have to do — the copy/paste, the reconciliation, the one-hundredth version of the same email — and turns it into systems that just run.

Easy Wins

2-3 week committed sprints with a business partner to build an n8n workflow or solution — the weekly reconciliation, the support-triage backlog, the recurring report nobody wants to draft.

R&D

Two weeks of protected time with a stakeholder to build something real, fast. Check-in at the end of week one. Prototype or lessons learned by the end of week two. The goal isn't production — it's proving the idea is worth continuing or shifting to a more formal initiative.

Initiatives

AI-first, cross-functional efforts that connect disparate systems and deliver value you can measure in hours saved. Usually driven by a pain point that touches multiple teams. Sized to ship inside a quarter — not to live on a roadmap forever.

Reworks

Workflows worth redesigning end-to-end with AI as a first-class participant — institutional knowledge stitched together in NotebookLM, intake reshaped so the model drafts and a human decides.

What I do

What I'm useful for.

Pointing AI at the boring problems

Pick the workflows where AI does real work — not demos — and ship them in days, not quarters, so people get an hour of their day back.

Scaling engineering teams

Help globally distributed engineering teams ship more without adding headcount — by fixing the operating model, not the people.

The systems behind the business

Lead the unglamorous work behind ERP, WMS, finance, and catalog so the tools running the business keep up with where the business is going.

Keeping everyone honest

Build the cadences, dashboards, and writing that let everyone answer 'what's in flight, what's blocked, what's done' without another meeting.

Current focus

Coaching more engineers into senior and lead roles — while we quietly retire the work that was never the best use of our business partners' time.

What I'm working on now
Let's talk

If any of this sounds like the problem in front of you, I'd love to compare notes.