Using AI to build Fulcrum workflows faster than ever

Your AI can already build on Fulcrum. You just haven’t told it to yet. Join us to see what happens when you do.

You don’t even like drag-and-drop? You’ll still understand this approach. You’re a full-stack developer? You’ll be surprised how little you need to build. Offline sync, GIS, validation, and security are already part of the platform, so what you build only has to cover the one piece that’s actually unique to your process.

How to build AI workflows fast

We’ll walk through what changes the moment your AI is connected: what it builds, what it inherits from Fulcrum automatically, and what to try first. Come with a process in mind and leave with a plan to build it. IT keeps the security and data structure they’re responsible for, your team builds only the piece that’s unique to the job, and whatever system of record sits on the other end gets the finished data without anyone building a separate tool to capture it.

We’ll cover:

• Why extending Fulcrum beats vibe-coding from scratch
• What you need to know before turning AI loose on a process
• What field processes make a good first AI workflow
• A full demo of the new AI-based workflow-building capabilities

Anyone ready to build AI workflows of their own will leave knowing where to start.

AI prompt used in the video

We’re Acer Ridge Electric. We’re building a new substation and extending a 12.47 kV three-phase feeder, CR-12-01, about two miles to serve a growing area with new solar, battery storage, and EV charging sites.

I want to run this as one program, from site selection through energization:

• Stakers pick pole locations along the route and record what each pole needs: height, class, framing, guying, soil, and clearances.
• We screen candidate DER sites and tie each to its nearest structure, so interconnection planning knows the distance.
• Construction crews set poles against the staked plan. We need to catch deviations before they become QA problems: wrong height or class, set too far from the stake, too shallow, or high ground resistance.
• Locates, vegetation clearing, and tailboards happen before crews dig. We already use Fulcrum for vegetation management and tailgate talks.
• Crews work offline. Everything has to roll up by project, circuit, and structure, so it lands cleanly in GIS and our work management system.

Help me:

1. Lay out the process: the phases, the steps, and what data each step hands to the next.
2. Draw it.
3. Recommend what to build first and why, and write the prompts that build it.

Then wait for my go before building.

Speaker

Jake Freivald
Vice President, Product Marketing

Jake Freivald’s twenty-five-year career in software has covered multiple technology specializations with a focus on data management and analytics. He places particular emphasis on helping business people understand the practical requirements of modernization. He has a B.S. in Electrical Engineering from Cornell University and lives with his family on Long Island, NY.