# FM — Full Site Content > A complete dump of FM's website content in markdown. Concatenated from every public page on https://www.buildfm.com. Generated dynamically and cached for 24 hours. ## https://www.buildfm.com # Software that compounds. We build the software, agents, and automations that turn your company’s daily work into a compounding asset. [Get Started](/get-started)[About Us](/about-us) The Shift ## Most of your company runs on people, not software. Your CRM works. Your ERP works. Your marketing platform, your support tools, your analytics. Each one does its job. But the work between those tools — the reports, the approvals, the operational picture — still lives in people’s heads and Slack threads. As you grow, that gets expensive. FM builds the layer that fills that gap. Software you own, shaped to how you actually operate, and designed to compound the work your team does every day. [See what we build](/solutions) Why FM ## What makes FM different? 01 ### Senior people, doing the work. No junior associates learning on your project. You work directly with the people building the system. 02 ### AI where it earns its place. We use AI as a real tool, not a sales pitch. It goes where it makes the system better, and stays out where it doesn't. 03 ### Built to last. You own what we build. We stay with the systems we ship as long as you need us to. No juniors. No layers. Just senior people doing the work. [Read About Us](/about-us) What Clients Say > “FM is building something truly differentiated — combining strong creative thinking with modern tooling and workflows that enabled us to launch our new site in just four weeks. They felt like a true extension of our team: highly strategic, deeply responsive, and committed to exceptional work.” ![Megan Malli](/_next/image?url=%2Fimages%2Fmegan-malli.jpeg&w=128&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) Megan Malli CEO, AnswerLab [Read the full case study →](/resource-center/31-day-replatform-case-study) ## FM's Newsletter Subscribe to our newsletter to stay updated with news about FM and our thoughts on the latest advancements in AI for business. Our Clients ## Trusted by teams building what's next We partner with ambitious teams to build custom software, implement AI strategies, and design intelligent automations that drive real results. ![AnswerLab](/_next/image?url=%2Fimages%2Fclients%2Fanswerlab-logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![ProCivica](/_next/image?url=%2Fimages%2Fclients%2FProCivica.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Trilith Studios](/_next/image?url=%2Fimages%2Fclients%2FTrilith_Studios_Logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Fantasy Interactive](/_next/image?url=%2Fimages%2Fclients%2Ffantasy_logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Alloy Marketing](/_next/image?url=%2Fimages%2Fclients%2FAlloy_Marketing_Logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Consume Media](/_next/image?url=%2Fimages%2Fclients%2Fconsume-media.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Brash Coffee](/_next/image?url=%2Fimages%2Fclients%2Fbrash-coffee.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Dagger](/_next/image?url=%2Fimages%2Fclients%2Fdagger.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![AnswerLab](/_next/image?url=%2Fimages%2Fclients%2Fanswerlab-logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![ProCivica](/_next/image?url=%2Fimages%2Fclients%2FProCivica.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Trilith Studios](/_next/image?url=%2Fimages%2Fclients%2FTrilith_Studios_Logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Fantasy Interactive](/_next/image?url=%2Fimages%2Fclients%2Ffantasy_logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Alloy Marketing](/_next/image?url=%2Fimages%2Fclients%2FAlloy_Marketing_Logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Consume Media](/_next/image?url=%2Fimages%2Fclients%2Fconsume-media.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Brash Coffee](/_next/image?url=%2Fimages%2Fclients%2Fbrash-coffee.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Dagger](/_next/image?url=%2Fimages%2Fclients%2Fdagger.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ## Latest News Latest updates and insights from FM [ ](/resource-center/software-that-takes-your-shape "Software That Takes Your Shape") Aug 17, 2026Thoughts [ ### Software That Takes Your Shape ](/resource-center/software-that-takes-your-shape) For thirty years we made people conform to software. Real-time UIs finally let it run the other way: software that composes itself for one person and takes their shape the longer they use it. Brian Fletcher Principal, Co-founder @ FM [ ](/resource-center/announcing-fm-labs "Announcing FM Labs") Jul 28, 2026Announcement [ ### Announcing FM Labs ](/resource-center/announcing-fm-labs) FM Labs is live at labs.buildfm.com. Free weekly workshops and one-on-one instruction for people who want to put AI to work in their own jobs. Tim Visconti Co-founder @ FM [ ](/resource-center/ai-persona-tool-case-study "From Generic GPT to Proprietary AI Asset: An AI Persona Tool Case Study") May 19, 2026Case Studies [ ### From Generic GPT to Proprietary AI Asset: An AI Persona Tool Case Study ](/resource-center/ai-persona-tool-case-study) How FM helped a tech-forward creative agency replace off-the-shelf custom GPTs with a proprietary AI persona platform—engineered against sycophancy, grounded in real audience research, built multi-tenant from day one, and now deployed across the agency's client portfolio. Brian Fletcher Principal / Co-founder @ FM ## Ready to build something? If you're feeling the pain of running your business on a stack that wasn't built to run a business, let's talk. [Let's Talk](/get-started)[Read About Us](/about-us) --- ## https://www.buildfm.com/about-us About FM # We built FM for a kind of work that didn't exist three years ago. For a long time, building custom software was slow, expensive, and risky. So companies bought SaaS for everything, and their best people held the operational picture together by hand. That's changing. We started FM to do the work that's now possible. What We Believe ## Every business does two kinds of work. **The work of knowing** is collecting information, noticing patterns, drawing inferences, figuring out what's true. **The work of deciding** is judgment, taste, accountability, choosing the right move when the picture is incomplete. For most of software's history, the work of knowing required a person. Software could store and calculate, but it couldn't synthesize or infer. So your best operators became the glue, holding everything together in their heads. That's the part that just changed. Software can now do the work of knowing. The work of deciding stays where it belongs, with the people running the business. We built FM to systematize the first kind of work completely, so our people and our clients' people can focus entirely on the second. How We Operate ## We run on the same kind of systems we build for clients. FM’s own operations run on FM OS, an internal system that handles the work of knowing automatically. FM’s team spends their time on the work that matters. ### We arrive prepared. Our systems pull together the relevant context, history, and open questions before every conversation. No fifteen minutes of catching up. ### Nothing falls through cracks. When a conversation ends, follow-up is already in motion. Notes captured, action items tracked, next steps queued. ### We move fast. Proposals go out while the conversation is fresh. Deliverables land while they're still relevant. ### Senior attention throughout. No junior staffing, no layered management. You work with the people doing the work. This is what the operational layer feels like from the inside. The way we work is a preview of what your own operation could become. Why We Built This ## A new kind of firm for a new kind of work. We're not a big firm trying to adapt. We're a small firm built for what comes next. ### Small by design. Senior, focused, directly accountable. No layers between you and the work. ### Built on our own systems. We run our operations on the same patterns we build for clients. Every engagement makes us better at the next one. ### Invested in what compounds. We measure success by what our clients can do tomorrow that they couldn't do yesterday. Our Team ## Leaders who helped architect the digital revolution. Our team has spent decades building software for organizations of all sizes - from startups to global enterprises. We've led engineering teams, launched platforms, and navigated complex transformations across nearly every industry. We started FM because we believe the way consultancies operate is about to change dramatically, and we wanted to build the firm we'd want to hire. Click on a team member to learn more. ![Brian Fletcher](/_next/image?url=%2Fimages%2Fbrian_fletcher.jpg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) View Bio ### Brian Fletcher Principal / Co-founder #### Brian Fletcher — Principal / Co-founder Brian Fletcher is a seasoned technology executive and co-founder of FM. With over two decades of leadership experience at global agencies and consultancies, Brian has a proven track record of steering world-class engineering teams to deliver transformative digital solutions for some of the world's leading brands (Google, CNN, Aon, Lowe's). His background spans nearly every industry vertical—from healthcare and consumer packaged goods to federal government and telecommunications—giving him a broad perspective on how to solve unique business challenges through technology. At FM, Brian is committed to redefining how software is built by leveraging AI-assisted development to push the boundaries of speed, quality, and impact. Brian's philosophy merges cutting-edge technology, a strong user-centric approach, and a relentless pursuit of innovation. This has led to breakthrough results throughout his career: whether launching global enterprise platforms, pioneering new digital products, or orchestrating complex integrations across marketing technology stacks. Brian holds a BA in Telecommunications from the University of Georgia and is passionate about continuous learning, having served as an instructor and advisory board member for The Creative Circus. A lifelong musician, Brian continues to play drums and create music. His dedication to both craft and culture underpins FM's mission: to empower businesses with custom-built software solutions that are faster, smarter, and truly transformative. [LinkedIn](https://www.linkedin.com/in/brianfletcher) ![Timothy Visconti](/_next/image?url=%2Fimages%2Ftimothy_visconti.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) View Bio ### Timothy Visconti Co-founder #### Timothy Visconti — Co-founder Timothy Visconti is a visionary entrepreneur and transformation strategist with over 20 years of experience helping organizations navigate disruption, adopt emerging technologies, and unlock human potential. As a co-founder of FM, he is focused on accelerating AI adoption, automating business processes, and modernizing legacy systems for companies ready to evolve. FM sits at the intersection of innovation and execution—helping clients bridge the gap between experimentation and real-world outcomes. From redefining operating models to building internal content flywheels and CX automation, Timothy's work enables businesses to grow smarter and move faster. Earlier in his founder career, Timothy also founded and scaled PeopleLift, an award-winning AI-powered workforce solutions firm, and launched Visconti Ventures, an early-stage investment arm backing high-growth AI startups. Through these platforms, he has built a reputation for clarity in execution, depth in strategy, and care in leadership. Guided by the belief that "1% outcomes only happen with passion, effort, resiliency, and care," Timothy continues to help bold organizations build what's next—with purpose and precision. [LinkedIn](https://www.linkedin.com/in/timothyvisconti) ![Adam Creeger](/_next/image?url=%2Fimages%2Fadam_creeger.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) View Bio ### Adam Creeger VP, Engineering #### Adam Creeger — VP, Engineering Adam Creeger is a seasoned engineering and product leader with a proven track record spanning both successful startups and large-scale operations, including leading Video teams at Facebook. Bridging the agility of startups with the rigor of big tech, Adam applies his expertise in AI-driven product development to deliver impactful, efficient solutions. He's passionate about leveraging emerging AI capabilities to streamline ideation and development, enabling teams to build better products—faster. [LinkedIn](https://www.linkedin.com/in/adamcreeger) ![Ryan Kellogg](/_next/image?url=%2Fimages%2Fryan-kellogg.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) View Bio ### Ryan Kellogg Principal #### Ryan Kellogg — Principal Ryan Kellogg enjoys making things people love & has spent 20+ years collaborating with ambitious clients & big picture dreamers to create immersive stories you can step inside of. By combining digital art & technology in bold new ways, Ryan strives to leverage technology to bring people closer together - not push them farther apart. Ryan has spoken, delivered keynotes & participated on panels at international design conferences such as SXSW, NRF, SEGD, Mobile World Congress, eBrandCON & more. With numerous publications & thought leadership pieces scattered throughout the web, as well as advisory partnership seats with higher education programs at SCAD, GSU, ULI & MASA to help enrich student programming & curriculum, Ryan actively participates in the design & creative engineering spaces at home & abroad. [LinkedIn](https://www.linkedin.com/in/ryankellogg) ![Eli Benveniste](/_next/image?url=%2Fimages%2Feli_benveniste.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) View Bio ### Eli Benveniste Senior Agentic Engineer #### Eli Benveniste — Senior Agentic Engineer Eli Benveniste is a senior agentic engineer at FM focused on turning ambitious product ideas into polished, production-ready software. He works across the full build process, from interaction design and prototyping to frontend development, CMS architecture, automation, integrations, and deployment. At FM, Eli helps teams move quickly from concept to launch, bringing a hands-on, systems-minded approach to every project. His recent work spans AI-assisted development workflows, custom web applications and CMS architectures, automated internal tooling, analytics and data integrations, and digital product experiences for clients ranging from enterprise brands to early-stage startups. Eli is especially interested in using new tools to make software faster to build, easier to maintain, and more useful to the people who rely on it. Whether prototyping interactive interfaces, structuring content systems, or shipping client-facing applications, he brings curiosity, craft, and a bias toward making things real. Eli holds a Bachelor of Science in Computer Science from the University of Georgia. [LinkedIn](https://www.linkedin.com/in/eli-benveniste/) ![Ziyi Shao](/_next/image?url=%2Fimages%2Fziyi_shao.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) View Bio ### Ziyi Shao Product Designer #### Ziyi Shao — Product Designer Ziyi Shao is a product designer at FM who helps turn early ideas into clear, usable products. Her work spans UX/UI design, interaction design, prototyping, visual systems, and brand development. At FM, Ziyi works on both internal tools and client-facing projects, including AI workflows, dashboards, resource platforms, and product interfaces. She also creates brand systems, presentations, and one-pagers that help teams explain product concepts and communicate their value clearly. Ziyi enjoys working closely with product and engineering teams to organize complex information and make new technology easier to understand and use. She holds a Master of Science in Human-Computer Interaction from the Georgia Institute of Technology and a Bachelor of Fine Arts in Design from the School of Visual Arts. [LinkedIn](https://www.linkedin.com/in/ziyishao/) ### Interested in joining FM? We're always looking for exceptional leaders who build. [Get in Touch](/get-started) FAQ ## Common questions about working with FM. ### Who is FM for? Small and mid-sized companies who need a senior partner for AI adoption, agent and automation work, or custom software builds. FM works best with companies between roughly 50 and 2,000 employees that have outgrown what off-the-shelf tools provide but don’t want to staff a full in-house team. ### What does an engagement with FM look like? Most engagements start with a 30-minute scoping call to figure out which pillar fits — AI Adoption, Agents & Automations, or Custom Software — then move into a focused 4–16 week build. FM is senior-only and outcomes-based, so the team you talk to is the team that ships the work. ### Will we own what FM builds? Yes. You own every line of code, the database schema, the deployment configuration, and the documentation. No per-seat licensing, no platform you have to keep paying FM to access. If you want FM to keep maintaining the system, that’s a separate retainer. ### Where is FM based? FM is an Atlanta, Georgia–based company. FM works with clients across the US, primarily remotely with regular video calls and async work in Slack and shared docs. Onsite workshops are available when the work benefits from being in the same room. ### How is FM different from a traditional consultancy? FM delivers working software and systems, not decks. The consultants are also the builders, so what FM recommends is grounded in what’s actually feasible in 4 weeks versus 4 months. Pricing is engagement-based, not headcount-based, so there’s no incentive to expand scope. For a deeper side-by-side, read [FM vs. a Traditional Consultancy: An Honest Comparison](/resource-center/what-makes-fm-different), which also lays out the cases where a traditional consultancy is the better fit. ### How do we get started? Reach out via the Get Started form for a 30-minute scoping call. No decks, no high-pressure sales — just a working conversation about whether FM is the right fit for your problem and how to move forward if it is. ## Ready to work together? Reach out and FM will set up a conversation. No decks, no hard sell — just a working session to see whether FM is the right fit. [Let’s Talk](/get-started)[Resource Center](/resource-center) --- ## https://www.buildfm.com/solutions What We Do # Three ways we help. Engagements usually start in one of three places. Most blend across all of them as the work unfolds. TL;DR Who FM is for Small and mid-sized companies who need a senior partner for AI and software work. What FM delivers AI Adoption, Agents & Automations, and Custom Software — picked together or separately. How FM works Senior-only team. AI-first delivery. You own everything FM builds. The Three Pillars [ ## AI Adoption Figure out where AI actually belongs before you build anything. Operational assessment, workforce enablement, and a roadmap you can execute. Learn more](/solutions/ai-adoption)[ ## Agents & Automations Take routine operator work off your team — copying data, building reports, routing approvals. AI agents where reasoning is needed; plain automation where it isn’t. Learn more](/solutions/agents-automations)[ ## Custom Software Bespoke software for when off-the-shelf doesn’t fit. Senior-only team, AI as a real collaborator, you own every line of code. Learn more](/solutions/custom-software) In Practice ## What this looks like, concretely. A sample of what AI Adoption, Agents and Automations, and Custom Software actually look like in practice. If something on this list sounds like your problem, that’s a good sign. ### Claude Enablement Get your team running on Claude. We're Claude Enablement Specialists — rollout, training, and the patterns that turn it into daily leverage. ### n8n & Zapier Automations Visual workflow automation set up the right way, so non-engineers can extend it without breaking what already works. ### Custom Agent Systems Custom agentic deployments and automations built on OpenClaw, Hermes, and other modern agent frameworks — the right tool for the job rather than locked into one. ### MCP Servers MCP servers built around your data and workflows. Connect Claude, ChatGPT, and your own agents to the systems they actually need — without one-off integrations for every tool. ### Technology Replatforms Shed legacy tech debt with AI-accelerated replatform projects — design, build, and content migration in weeks instead of months. ### Custom AI Knowledge Bases Your team's knowledge, searchable and conversational, without leaking it into someone else's training data. ### Customer Service Enablers Agents and copilots that handle the routine and route the rest to your team with context already loaded. ### Content Operations AI-powered content production that scales without adding headcount. Plan, draft, and ship without burning out your writers. ### AI Agents for Sales Ops Lead routing, CRM hygiene, and pipeline reporting handled by agents instead of analysts. Our Clients ## Trusted by teams building what's next We partner with ambitious teams to build custom software, implement AI strategies, and design intelligent automations that drive real results. ![AnswerLab](/_next/image?url=%2Fimages%2Fclients%2Fanswerlab-logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![ProCivica](/_next/image?url=%2Fimages%2Fclients%2FProCivica.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Trilith Studios](/_next/image?url=%2Fimages%2Fclients%2FTrilith_Studios_Logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Fantasy Interactive](/_next/image?url=%2Fimages%2Fclients%2Ffantasy_logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Alloy Marketing](/_next/image?url=%2Fimages%2Fclients%2FAlloy_Marketing_Logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Consume Media](/_next/image?url=%2Fimages%2Fclients%2Fconsume-media.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Brash Coffee](/_next/image?url=%2Fimages%2Fclients%2Fbrash-coffee.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Dagger](/_next/image?url=%2Fimages%2Fclients%2Fdagger.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![AnswerLab](/_next/image?url=%2Fimages%2Fclients%2Fanswerlab-logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![ProCivica](/_next/image?url=%2Fimages%2Fclients%2FProCivica.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Trilith Studios](/_next/image?url=%2Fimages%2Fclients%2FTrilith_Studios_Logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Fantasy Interactive](/_next/image?url=%2Fimages%2Fclients%2Ffantasy_logo.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Alloy Marketing](/_next/image?url=%2Fimages%2Fclients%2FAlloy_Marketing_Logo.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Consume Media](/_next/image?url=%2Fimages%2Fclients%2Fconsume-media.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Brash Coffee](/_next/image?url=%2Fimages%2Fclients%2Fbrash-coffee.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) ![Dagger](/_next/image?url=%2Fimages%2Fclients%2Fdagger.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) For Buyers ## Still evaluating AI consultancies? [Buyer’s framework ### How to Choose an AI Consultancy A practical framework with a scoring rubric, red flags, and the questions that reveal what kind of partner you’re really hiring. Read the guide](/resource-center/how-to-choose-an-ai-consultancy)[Honest comparison ### FM vs. a Traditional Consultancy A side-by-side comparison — and an honest list of cases where a traditional consultancy is actually the better fit. Read the comparison](/resource-center/what-makes-fm-different) What We Don't Do ## We say no a lot. A short list of things we're not the right firm for. - Renting senior people as staff augmentation - Advisory engagements that end in a deck instead of working software - Platforms or stacks our clients can't operate without us - Domains we don't actually know If you need any of those, we can usually point you to someone good. ## Ready to build something? Whether you’re exploring AI adoption, automating workflows, or building custom software, we’re here to help you take the next step. [Let’s Talk](/get-started)[Explore Our Expertise](/expertise) --- ## https://www.buildfm.com/solutions/ai-adoption AI Adoption # Figure out where AI actually belongs. Before you build, decide what’s worth building. FM finds the highest-leverage AI opportunities in your business and hands back a roadmap you can execute — with us, with another partner, or in-house. TL;DR Who it’s for Mid-sized companies starting with AI, or stuck after early experiments. What FM delivers Operational assessment + workforce enablement, with a prioritized roadmap. Engagement length 4–8 weeks for assessment; ongoing for enablement. ## What is AI Adoption? AI adoption is the work that comes before you build anything. It’s mapping how your business runs today, identifying where AI actually fits, and giving your team the language and frameworks to evaluate tools without falling for the hype. Most companies skip this. They roll out ChatGPT licenses, run a few pilots, and end up with scattered experiments that don’t compound. The result is energy spent without leverage gained, and a team that’s increasingly skeptical of the whole project. FM treats AI adoption as a planning discipline, not a kickoff event. We learn how your business runs across your tools and your people. We find where time and money are leaking. You walk away with a prioritized plan you can actually execute. ![FM leading an AI workshop for Trilith Studios with Dan T. Cathy.](/_next/image?url=%2Fimages%2Ftrilith_workshop.jpeg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) Leading an AI workshop for Trilith Studios with Dan T. Cathy. ## When do you need AI Adoption? - AI is being used ad hoc across your team with no shared playbook. - Your pilots work in demos but stall at rollout. - Leadership wants an AI strategy that isn’t a vendor pitch deck. - You’re deciding whether to buy or build agentic systems. - Your team is anxious about AI and needs frameworks, not another demo. ## When you don’t. - You already know what to build. Skip to Agents & Automations or Custom Software. - You want a deck. FM delivers plans that get executed. - You’re already shipping agents and internal tools. You need build capacity, not an assessment. - You want a one-off training. Real enablement takes more than a workshop. ## How does FM approach AI Adoption? AI Adoption is consultative work, not engineering work. FM uses a set of frameworks and methodologies — not a stack of software — to figure out where AI belongs in your business and what your team needs to use it well. ### Tools and frameworks FM uses #### AI Maturity Assessment Places your organization on a maturity curve from ad hoc experiments to systematized leverage. Sets a shared baseline for what "good" looks like at your stage. #### Operational Mapping A structured walk through how your business actually runs across tools, teams, and processes. The basis for every recommendation FM makes about where AI fits. #### Opportunity Scoring Rubric A consistent way to evaluate AI use cases on ROI, effort, dependencies, and reversibility. Replaces opinion-based prioritization with a comparable rubric. #### Build vs. Buy vs. Train Decision Framework For each opportunity, a structured way to decide whether to build custom, adopt existing tools, or invest in training your team. Avoids defaulting to the most expensive option. #### Workforce Readiness Diagnostic Measures where your team is on AI literacy and identifies the gaps that need to close before any rollout will stick. Role-specific, not generic. #### Adoption Playbooks Concrete patterns for how specific roles — sales, ops, marketing, exec — actually use AI in their day-to-day work. Living documents, not training slides. ### What an engagement looks like 2–4 weeks #### Operational Assessment - Process map of how your business runs today, across tools and teams - Time-and-money leak analysis: where the work of knowing is most expensive - Prioritized opportunity list, each scored for ROI, effort, and dependencies - Recommended build sequence — what to do first, second, and never 4–8 weeks #### Workforce Enablement - Role-based playbooks for sales, ops, marketing, exec — whoever needs them - AI evaluation framework your team can apply to future tools without FM - Working sessions on your team’s real work, not toy examples - A baseline AI policy and governance recommendation, drafted with you Specific shapes this work takes ### Claude Enablement Get your team running on Claude. FM are Claude Enablement Specialists — rollout, training, and the patterns that turn it into daily leverage. ### Custom AI Knowledge Bases Your team's knowledge, searchable and conversational, without leaking it into someone else's training data. ### Content Operations AI-powered content production that scales without adding headcount. Plan, draft, and ship without burning out your writers. [ ![FM running an AI workshop with the team at Trilith Studios.](/_next/image?url=%2Fimages%2Fposts%2Ftrilith_studios.jpg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) Featured case study ### Trilith Studios — AI in Action Workshop How Dan T. Cathy and the Trilith team learned to use AI in their day-to-day work — a workforce enablement engagement grounded in their real production challenges. Read the case study ](/resource-center/trilith-studios-case-study) ## Frequently asked questions. ### How much does an AI adoption engagement cost? Pricing depends on scope and team size, so FM shares a specific range after a 30-minute scoping call. As a frame of reference: assessment engagements are typically four to six weeks of focused work; enablement is structured as a retainer or per-cohort. ### Who participates from our side? Assessment needs access to leadership plus four to eight operators across the teams whose work is most likely to change. FM does focused interviews and shadowing — usually 30–60 minutes per person. Enablement involves whoever will actually use AI in their day-to-day work. ### What do the deliverables actually look like? For assessment: a written report plus a prioritized roadmap, with each opportunity scored for ROI, effort, and dependency on other work. For enablement: role-specific playbooks, an AI evaluation framework, and live working sessions on your team’s real work. Nothing that sits in a SharePoint folder. ### Will our data stay private? Yes. FM signs NDAs, works in your environments where possible, and recommends models with no-training guarantees (Claude API, ChatGPT Enterprise, and similar) for any work that touches sensitive data. Data flow is documented in every recommendation. ### What if we’re not technical? That’s the most common case for AI adoption work, and it’s fine. FM doesn’t expect your team to know AI inside out — the job is to translate between the technology and the business so you can make confident decisions. ### How is this different from a McKinsey-style AI strategy engagement? FM delivers plans that get executed, not decks that get filed. The consultants are also the builders, so what FM recommends is grounded in what’s actually feasible in 4 weeks versus 4 months. And pricing is engagement-based, not headcount-based, so there’s no incentive to expand scope. ## Ready to talk about AI Adoption? Reach out and we’ll set up a conversation. No hard sell, no decks — just a working session to see whether FM is the right fit. [Let’s Talk](/get-started)[See all solutions](/solutions) ### Related pillars - [Agents & Automations](/solutions/agents-automations) - [Custom Software](/solutions/custom-software) --- ## https://www.buildfm.com/solutions/agents-automations Agents & Automations # Give your team back their best hours. FM designs and builds the systems that take routine operator work off your team — copying data, building reports, routing approvals, synthesis. AI agents where the work needs reasoning. Plain automation where it doesn’t. TL;DR Who it’s for Small and mid-sized companies whose teams are buried in routine operational work. What FM delivers Agents and automations built on the right stack for each job — not locked into one. Engagement length 4–12 weeks per build. ## What is Agents & Automations? Every business runs on two kinds of work. The work of knowing — collecting information, watching for patterns, assembling reports, routing approvals — used to require a person. The work of deciding — judgment, taste, accountability — still does. Agents and automations move the first kind off your team so they can focus on the second. The distinction between an agent and an automation is practical, not philosophical. Automations follow rules: when X happens, do Y. Agents reason: figure out the right Y based on context. FM uses both, picks the right one for each job, and combines them where it makes sense. Most real systems are a mix. Done well, the result isn’t a chatbot bolted onto your business. It’s the boring parts of your operators’ day going away — and the work that’s left being more interesting, more important, and more leveraged. Click to expand Watch FM co-founder Tim Visconti on how to get started with automations. Tap the video to play in full screen. ## When do you need Agents & Automations? - Your team copies data between systems for hours every week. - Reports that should take an hour take three days, every month. - Approval workflows depend on someone remembering to ping someone. - Lead routing, CRM hygiene, or pipeline reporting eats your operators’ time. - You have a clear, repeated process that someone keeps having to babysit. - You want to deploy agents that reach into your business systems, but don’t know where to start. ## When you don’t. - The work changes daily and requires judgment in every case. Automating it will create more problems than it solves. - You don’t yet have a stable process to automate. Start with AI Adoption to find the right targets first. - You want a low-code DIY effort. FM can help you scope one, but the right partner for that is your own ops team plus a Zapier seat. - The work happens fewer than a dozen times a year. The build cost won’t pay back. ## How does FM approach Agents & Automations? Agents and Automations is engineering work, so the tools matter. FM picks the right stack for each job — visual automation where non-engineers will extend it, agent frameworks where reasoning is needed, custom code where neither fits. ### Tools and frameworks FM uses #### n8n Visual workflow automation. Used when the rules are clear and the system needs to be readable and extendable by non-engineers on your team. #### MCP (Model Context Protocol) The connective tissue between AI models and your business systems. FM builds custom MCP servers so Claude, ChatGPT, or your own agents can reach the data they need without one-off integrations. #### OpenClaw / Hermes Custom agent frameworks. OpenClaw handles complex, multi-step work where an agent needs to coordinate tools, manage state, and recover from failure. Hermes handles narrower, scoped deployments where OpenClaw would be overkill. #### Claude (and other frontier models) The reasoning layer. FM evaluates which model fits each use case rather than defaulting to a single provider. #### Evals and observability Custom evaluation suites and structured logging built into every system FM ships. The difference between a demo and a production system is knowing when it breaks before your users do. #### Custom code For the cases where no framework is the right fit. FM writes production code in TypeScript and Python rather than forcing every problem into a tool that wasn’t built for it. ### How an engagement runs Phase 1 · 1–2 weeks #### Discovery - Workflow mapped end-to-end, including the unwritten steps people do from memory - Decision on tool stack: visual automation, agent framework, custom code, or a mix - Risk and failure-mode analysis: what happens when the system gets it wrong - Acceptance criteria written in plain language, not technical specs Phase 2 · 2–6 weeks #### Build - Working system, deployed in your environment, exercised against real data - Human-in-the-loop checkpoints where the work needs judgment - Monitoring and logging your team can actually read - Iteration cycles based on what shows up under real use, not just demo data Phase 3 · 1–2 weeks #### Handoff - Documentation that lets your team operate and extend the system without FM - Training sessions with the operators who will use it day-to-day - A maintenance plan: what FM owns ongoing vs. what your team owns - A retrospective on what worked, what didn’t, and what to build next Specific shapes this work takes ### n8n Implementations Visual workflow automation set up the right way, so non-engineers can extend it without breaking what already works. ### Custom Agent Systems Custom agentic deployments and automations built on OpenClaw, Hermes, and other modern agent frameworks — the right tool for the job rather than locked into one. ### MCP Servers MCP servers built around your data and workflows. Connect Claude, ChatGPT, and your own agents to the systems they actually need — without one-off integrations for every tool. ### AI Agents for Sales Ops Lead routing, CRM hygiene, and pipeline reporting handled by agents instead of analysts. ### Customer Service Enablers Agents and copilots that handle the routine and route the rest to your team with context already loaded. ### Content Operations AI-powered content production that scales without adding headcount. Plan, draft, and ship without burning out your writers. [ ![FM’s AI Persona Tool — turning scattered GPT experiments into a proprietary AI asset.](/_next/image?url=%2Fimages%2Fposts%2Fai-persona-tool-case-study.jpg&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) Featured case study ### AI Persona Tool — From Generic GPT to Proprietary AI Asset How FM built a custom AI persona system that turned a client’s scattered GPT experiments into a proprietary, reusable asset their team could actually rely on. Read the case study ](/resource-center/ai-persona-tool-case-study) ## Frequently asked questions. ### What’s the difference between an agent and an automation, and how do you decide which to use? Automations follow rules; agents reason. If the work is "when X, do Y" with clear inputs and outputs, automation is faster, cheaper, and more reliable. If the work needs the system to figure out the right next step — pulling context from multiple places, handling exceptions, or generating language — an agent earns its place. Most real systems combine both. FM picks the simpler tool first and adds reasoning only where it pays back. ### How much does an agents and automations engagement cost? It depends on scope, the systems involved, and how much custom code is required. FM shares a specific range after a 30-minute scoping call. As a frame of reference: most engagements run 4–12 weeks of focused build time and are priced on outcomes rather than hours. ### Will we own the code and the system after the engagement? Yes. You own everything FM builds — the code, the configurations, the documentation. There is no licensing, no per-seat fee, no platform you have to keep paying FM to access. If you want FM to keep maintaining the system, that’s a separate retainer; if you want to take it in-house, the handoff is built into the engagement. ### What if our team doesn’t know n8n, MCP, or agent frameworks? Most clients don’t. The handoff phase exists for exactly this reason — FM documents what was built, trains your operators, and structures the system so non-engineers on your team can extend it. Where deeper technical work is needed later, you can come back to FM, hire someone, or use the documentation to evaluate other partners. ### How do you handle the AI doing something wrong — hallucinations, bad data, or unexpected behavior? Three ways. First, FM builds human-in-the-loop checkpoints wherever the cost of being wrong is meaningful. Second, the systems log their reasoning so when something goes sideways you can see why. Third, FM doesn’t pretend the AI is reliable on tasks where it isn’t — automation handles the deterministic parts; reasoning is reserved for places where it genuinely earns its place. ### Do you support the systems you build after launch? Yes, on a retainer basis. Many clients keep FM engaged for ongoing monitoring, optimization, and new feature work. Others take the system in-house once the team is up to speed. Either way is fine — the handoff is structured so you have a real choice. ## Ready to talk about Agents & Automations? Reach out and we’ll set up a conversation. No hard sell, no decks — just a working session to see whether FM is the right fit. [Let’s Talk](/get-started)[See all solutions](/solutions) ### Related pillars - [AI Adoption](/solutions/ai-adoption) - [Custom Software](/solutions/custom-software) --- ## https://www.buildfm.com/solutions/custom-software Custom Software # When off-the-shelf isn’t the answer. FM builds bespoke software for mid-sized companies — when the right SaaS doesn’t exist, when the one you’ve been using stopped fitting, or when the system you depend on is too old to keep extending. Senior-only team, AI as a real collaborator, and you own every line of code. TL;DR Who it’s for Small and mid-sized companies who need bespoke software or are replatforming off something that no longer fits. What FM delivers Discovery and prototyping, then production build by senior engineers with AI as a collaborator. Engagement length 8–16 weeks for replatforms; longer for net-new platforms. ## What is Custom Software? Custom software is what you build when no off-the-shelf answer fits — or when the answer that used to fit stopped fitting years ago. FM builds the software your business actually runs on, not a generic version of it that you then have to bend the business around. Two changes have made custom software accessible again. AI as a real collaborator has cut build time by a meaningful margin — not by replacing engineers, but by giving senior engineers more leverage. And the divide between SaaS and bespoke has collapsed: modern tooling means a custom system can be as fast to ship and as easy to maintain as buying something off the shelf. FM does not build prototypes that need to be rebuilt to ship. The work goes to production. Senior product managers, product designers, and engineers work as one team across every engagement — not a sequence of handoffs between siloed specialists. Your team operates and extends the system after launch. You own the code, the data, the roadmap, and the relationship with everything underneath it. Click to expand Watch FM Principal Brian Fletcher on the third path for software — why custom is back on the table for small and mid-sized companies. Tap the video to play in full screen. ## When do you need Custom Software? - The SaaS you’ve been using stopped fitting your business years ago. - No vendor offers what you actually need, only adjacent things. - Your team is hacking around a platform with spreadsheets and shadow IT. - You depend on a system that’s too old to keep extending safely. - Compliance, strategy, or IP concerns mean you need to own the code outright. - You’re paying for ten times more features than you use, and the few you actually need don’t exist. ## When you don’t. - A clear SaaS fit exists at reasonable cost. Buy it instead. - You can’t commit a small stakeholder team to weekly demos and feedback. The work won’t land without you. - You want offshore body-shop pricing. FM is senior-only by design and doesn’t compete on rate. - You’re early enough that a vibe-coded MVP would suffice. Come back when production stakes are real. ## How does FM approach Custom Software? Custom Software is product, design, and engineering working as one team — not a sequence of handoffs between siloed specialists. The stack matters too: FM picks proven, boring tools where they fit and reaches for newer ones only where the benefit is real. The bar is production-grade from day one, not "we’ll harden it later." ### Tools and frameworks FM uses #### Next.js + TypeScript The default frontend and full-stack framework. Server components, server actions, and edge-ready by default. Type-safe end to end. #### Tailwind CSS + shadcn/ui A design system that doesn’t slow you down. Composable components, easy to brand, accessible by default. #### Drizzle ORM + Postgres Type-safe data layer with explicit migrations. The boring, durable choice — important for code that needs to last. #### Vercel Deployment, hosting, edge functions, and image optimization handled by the platform. Less infrastructure to maintain, more time on the actual software. #### Claude Code (AI collaborator) AI integrated into the engineering workflow, not bolted on. FM uses Claude Code to accelerate routine implementation so senior engineers focus on architecture and judgment calls. #### Tests, evals, and observability Built in from day one. Type checks, integration tests, runtime logs, and AI-specific evals where reasoning is in the loop. So you know what’s working and what isn’t. ### How an engagement runs Phase 1 · 1–3 weeks #### Discovery and Prototyping - Working prototype of the core workflow you can react to, not just slides - Scope, architecture, and stack decisions made explicit and written down - Risk and unknowns list, with how each will be de-risked during build - A go/no-go decision point — proceed to build, revise scope, or stop Phase 2 · 6–14 weeks #### Production Build - Working software in your environment, demoed weekly with your stakeholders - Iteration cycles based on what you see, not what was speculated about upfront - Production-grade code with tests, observability, and documentation as it’s written - Real users on real data before launch, not the day after Phase 3 · 1–2 weeks + ongoing #### Launch and Stewardship - Launch coordinated with your team, including any data migration or cutover - Documentation and training for your operators and your developers - A maintenance plan: what FM owns ongoing vs. what your team owns - Optional retainer for ongoing enhancements, or a clean handoff if you want to take it in-house Specific shapes this work takes ### Technology Replatforms Shed legacy tech debt with AI-accelerated replatform projects — design, build, and content migration in weeks instead of months. ### Bespoke Product Development Zero-to-one product development for founders and operators building net-new products from the ground up. Discovery, prototype, and production build — you own the code and the roadmap from day one. ### Custom AI Knowledge Bases Your team's knowledge, searchable and conversational, without leaking it into someone else's training data. [ ![ProCivica leadership with the custom learning management platform FM built.](/_next/image?url=%2Fimages%2Fposts%2Fchip_caleb.png&w=3840&q=75&dpl=dpl_GeQVedcQJrB4Vi1jwbZJoJqRqv1u) Featured case study ### ProCivica — Scaling Nationally with Custom Software How FM partnered with ProCivica to build a custom learning management platform that unlocked national expansion and cut operational overhead. Read the case study ](/resource-center/procivica-case-study) ## Frequently asked questions. ### How long does a custom software engagement take? Replatforms typically run 8–16 weeks. Net-new platforms vary more — anywhere from 12 weeks for a focused tool to several months for a full system. The Discovery and Prototyping phase exists in part to give you an honest range before any large commitment. ### How much does it cost? It depends on scope and complexity, so FM shares a specific range after a 30-minute scoping call. Engagements are priced on outcomes and milestones rather than hours, so the number is the number — no surprise overruns and no incentive for FM to stretch the timeline. ### Will we own the code and IP? Yes. You own every line of code, the database schema, the deployment configuration — everything. No license fees, no per-seat charges, no platform you have to keep paying FM to access. The code lives in your repository, on your accounts, with your team having full access from day one. ### Who actually does the work? Senior engineers, full stop. FM does not have a junior staffing tier or use AI as cover for outsourcing to less experienced people. The trade-off is honest: FM costs more per week than a body shop, and FM delivers in a fraction of the calendar time. ### What about ongoing maintenance after launch? You have a choice. Many clients keep FM on a small retainer for monitoring, security patches, and incremental enhancements. Others take the system fully in-house once their team is up to speed. The handoff phase is structured so either path works — you’re not locked in either way. ### What if we want our in-house team to take over the system? That’s a supported option from day one. The documentation, code quality, and architectural choices are made with handoff in mind. FM also runs training sessions during the Launch and Stewardship phase so your developers understand the system at the level needed to extend it without us. ## Ready to talk about Custom Software? Reach out and we’ll set up a conversation. No hard sell, no decks — just a working session to see whether FM is the right fit. [Let’s Talk](/get-started)[See all solutions](/solutions) ### Related pillars - [AI Adoption](/solutions/ai-adoption) - [Agents & Automations](/solutions/agents-automations) --- ## https://www.buildfm.com/expertise Our Expertise # We've shipped a lot of software. Now we ship a new kind. Two decades of building production systems for companies of every size. Now applied to the work that software couldn't do until recently. Our Craft ## We deliver software, not slides. Most firms in this space deliver recommendations. FM delivers working systems. The mindset is different, the engagement is different, and the result is different. FM has learned, sometimes painfully, what separates projects that ship from projects that stall. The biggest one: the best solutions aren’t complicated. They’re the ones that make a hard problem feel obvious in retrospect. The Unlock ## Software can think now. That changes everything we build. For decades, software did calculation and storage. The reasoning, the judgment, the pattern-matching, all of it lived in people's heads. That's not true anymore. Software can synthesize, infer, and handle the messy cases that don't fit a rule. It can take on real cognitive work, the kind that used to require a senior operator. That's the change that makes our work possible. It's also the change most companies haven't figured out how to use yet. We help them. Before Before Software stored what people decided. The reasoning, synthesis, and judgment lived in the operator's head. The software was the file cabinet. Now Now Software does the reasoning, too. Systems that synthesize and infer. The operator's job moves up the stack, from doing the work of knowing to acting on it. The Team Behind the Build ## Four disciplines. One team. On every engagement. FM staffs senior across four disciplines. There are no junior hand-offs and no proposal team passing the work to a delivery team. The people who scope the work are the people who ship it. ### Principals Strategic ownership from scoping through stewardship. Two decades leading software at global agencies, big tech, and enterprise transformation programs. Principals stay on the call. Architecture, scope, and the hard tradeoffs are made by the people doing the work. - System architecture - Build vs. buy calls - Roadmap & sequencing - Engagement stewardship ### Agentic Engineers Build the systems. AI-native, full-stack. Senior engineers fluent in the modern web stack and the agentic toolchain. They write production code, design schemas, integrate models, and ship features end-to-end. AI is built into how they work, not bolted onto the deliverable. - Next.js / TypeScript apps - Agent orchestration & MCP - Schemas, data, integrations - Evals, observability, CI/CD ### Product Strategy Translates business problems into shippable scope. Discovery, opportunity scoring, build-vs-buy frameworks, phasing. Strategists who have done transformations at scale and know what actually ships in six weeks versus what stalls at sixteen. - AI maturity assessments - Operational mapping - Opportunity scoring - Phasing & success criteria ### Design Product, interaction, brand — no handoff. Designers who lead product thinking from week one, not pixel pushers brought in late. Backgrounds span immersive work for global brands, design systems for production software, and brand identity for early-stage products. - Product UX & prototyping - Design systems - Brand identity - Design-to-code handoff The Stack ## Boring where it should be. Sharp where it counts. FM picks proven, durable tools for the work that needs to last, and reaches for newer ones only where the benefit is real. The same stack underpins every pillar — Custom Software, Agents & Automations, and AI Adoption — so phases hand off cleanly instead of starting over. ### Languages & Frameworks Modern TypeScript on the web, Python where data and ML live. - TypeScript / JavaScript — Node, edge, and the browser - Python — Data pipelines, ML, scripting - Next.js (App Router) + React — Server components, server actions - Tailwind CSS + shadcn/ui — Composable, accessible design system - Node, Bun, and edge runtimes ### AI & Agent Tooling Frontier models and the agentic ecosystem around them. - Claude, GPT, Gemini — Frontier models via direct APIs or gateways - MCP (Model Context Protocol) — Tool and data integration for agents - n8n, Zapier — Visual workflow orchestration and SaaS-to-SaaS automation - Claude Code, Codex — AI inside the engineering workflow itself - Custom evals & tracing — LLM observability where reasoning is in the loop ### Data & Infrastructure Boring where it should be. Type-safe, observable, yours. - Postgres + Drizzle ORM — Type-safe data, explicit migrations - Vercel — Deployment, edge functions, image optimization - AWS, GCP, Azure — Cloud experience across all three majors when the workload calls for it - PostHog — Product analytics and feature flags - Resend — Transactional email - Tests, observability, CI/CD — First-class from day one, not bolted on ### Solution Types What the stack adds up to in the wild. - Custom web applications & internal tools - AI agents, copilots, and assisted workflows - Operational automations & integrations - Replatforms from legacy SaaS or homegrown systems - Custom knowledge bases & retrieval systems - Design systems and brand-to-code work The stack evolves. What stays constant is the bar: production-grade from day one, owned by you, and shaped by what the problem actually needs. What We Bring ## The mindset behind everything we build. 01 ### Systems Thinking Every problem sits inside a larger system. We look for the fix that makes the whole thing better, not just the part you asked about. 02 ### Pragmatic AI AI is a tool, not a strategy. We use it where it earns its place and leave it out where it doesn't. 03 ### Delivery Over Discussion We're not here to produce findings. We're here to produce working software, and stay with it until it's running. 04 ### Compound Thinking The best systems make tomorrow's work easier than today's. We design for that. How We Work ## Wherever you are, we can probably help. ### If you're exploring You're trying to figure out where AI actually belongs in your business. We'll help you build the map. ### If you're ready to build You know the opportunity and you need a team that ships. We embed and get production systems live. ### If you're stuck Something's not working, or you inherited a mess. We've been there. We'll help you find the path forward. ## Ready to Build Something? Whether you're exploring AI adoption, automating workflows, or building custom software, we're here to help you take the next step. [Let's Talk](/get-started)[Learn About FM](/about-us) --- ## https://www.buildfm.com/resource-center Insights & Resources # Resource Center Insights, guides, and success stories from the team at FM. Featured Article [](/resource-center/software-that-takes-your-shape "Software That Takes Your Shape") Aug 17, 2026Thoughts [ ### Software That Takes Your Shape ](/resource-center/software-that-takes-your-shape) For thirty years we made people conform to software. Real-time UIs finally let it run the other way: software that composes itself for one person and takes their shape the longer they use it. Brian Fletcher Principal, Co-founder @ FM AllAnnouncementCase StudiesEventsFAQsHow-to GuidesThoughts [](/resource-center/announcing-fm-labs "Announcing FM Labs") Jul 28, 2026Announcement [ ### Announcing FM Labs ](/resource-center/announcing-fm-labs) FM Labs is live at labs.buildfm.com. Free weekly workshops and one-on-one instruction for people who want to put AI to work in their own jobs. Tim Visconti Co-founder @ FM [](/resource-center/ai-persona-tool-case-study "From Generic GPT to Proprietary AI Asset: An AI Persona Tool Case Study") May 19, 2026Case Studies [ ### From Generic GPT to Proprietary AI Asset: An AI Persona Tool Case Study ](/resource-center/ai-persona-tool-case-study) How FM helped a tech-forward creative agency replace off-the-shelf custom GPTs with a proprietary AI persona platform—engineered against sycophancy, grounded in real audience research, built multi-tenant from day one, and now deployed across the agency's client portfolio. Brian Fletcher Principal / Co-founder @ FM [](/resource-center/31-day-replatform-case-study "From Kickoff to Launch in 31 Days: The AnswerLab Replatform") Apr 14, 2026Case Studies [ ### From Kickoff to Launch in 31 Days: The AnswerLab Replatform ](/resource-center/31-day-replatform-case-study) How FM replatformed AnswerLab's marketing website in 31 days—migrating 400+ content assets, shipping a living brand experience, and hitting a non-negotiable banker-meeting deadline. Brian Fletcher Principal / Co-founder @ FM [](/resource-center/saas-leak "The SaaS Leak: Why Operations are Moving from Fixed Subscriptions to Disposable Leverage") Mar 24, 2026Thoughts [ ### The SaaS Leak: Why Operations are Moving from Fixed Subscriptions to Disposable Leverage ](/resource-center/saas-leak) The cost of building software has collapsed, but the cost of generic SaaS is rising. Here is why leading teams are ripping out 'point solutions' and replacing them with custom connective tissue. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/good-enough-is-not-enough "Good Enough Is Not Enough") Mar 11, 2026Thoughts [ ### Good Enough Is Not Enough ](/resource-center/good-enough-is-not-enough) AI just made "passable" work free. It’s time to move beyond the middle and embrace the Precision Standard. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/markdown-is-eating-the-world "Markdown is Eating the World") Jan 31, 2026Announcement [ ### Markdown is Eating the World ](/resource-center/markdown-is-eating-the-world) We rebuilt our website to speak two languages — human and machine. Here's why markdown is becoming the universal format for business. FM Engineering [](/resource-center/the-high-cost-of-free-code "The High Cost of Free Code: Why Builders Must Become Architects") Jan 29, 2026Thoughts [ ### The High Cost of Free Code: Why Builders Must Become Architects ](/resource-center/the-high-cost-of-free-code) When the cost of building software drops to near zero, the bottleneck is no longer 'can we build it?' but 'should we build it?' Brian Fletcher Principal, Co-founder @ FM [](/resource-center/system-of-intelligence "We Built Our Own Operating System. Here's Why.") Jan 20, 2026Thoughts [ ### We Built Our Own Operating System. Here's Why. ](/resource-center/system-of-intelligence) How FM stopped fighting our SaaS stack and built an agentic layer that actually runs our business. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/vibe-check-is-not-a-strategy "The 'Vibe Check' is Not a Strategy") Jan 11, 2026Thoughts [ ### The 'Vibe Check' is Not a Strategy ](/resource-center/vibe-check-is-not-a-strategy) Moving from 'it seems to work' to 'we can prove it works.' Why Product Owners must shift from PRDs to Success Rubrics in the age of AI agents. Engineering FM [](/resource-center/build-vs-buy-agent-age "Build vs. Buy in the Age of AI Agents") Dec 17, 2025Thoughts [ ### Build vs. Buy in the Age of AI Agents ](/resource-center/build-vs-buy-agent-age) The debate over whether to build custom software or buy SaaS just got more complicated. A high-profile CMS migration shows us what to build, what to buy, and where the real opportunity lies. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/human-architect-ai-builder "The Human Architect & The AI Builder") Dec 5, 2025Case Studies [ ### The Human Architect & The AI Builder ](/resource-center/human-architect-ai-builder) How FM and Fantasy used an intentional "Human-in-the-Loop" collaboration model to deliver a massive multi-brand consolidation project in just six weeks. Adam Creeger VP, Engineering [](/resource-center/scaling-without-headcount "Scaling Operations Without Proportionally Increasing Headcount") Nov 3, 2025How-to Guides [ ### Scaling Operations Without Proportionally Increasing Headcount ](/resource-center/scaling-without-headcount) Break the linear relationship between volume and headcount by systematically identifying and automating operational bottlenecks. Tim Visconti Co-founder @ FM [](/resource-center/ai-development-timelines "How Long Does It Actually Take to Build Custom Software with AI-Empowered Development?") Nov 1, 2025FAQs [ ### How Long Does It Actually Take to Build Custom Software with AI-Empowered Development? ](/resource-center/ai-development-timelines) Modern AI-empowered development has completely changed the timeline calculus. What used to take six to nine months can now be done in 8-10 weeks. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/procivica-case-study "How ProCivica Scaled Nationally with Custom Software: A Case Study") Oct 25, 2025Case Studies [ ### How ProCivica Scaled Nationally with Custom Software: A Case Study ](/resource-center/procivica-case-study) How FM partnered with ProCivica to build a custom learning management platform that unlocked national expansion and transformed operational efficiency. Brian Fletcher Principal / Co-founder @ FM [](/resource-center/preparing-team-for-ai-adoption "Preparing Your Team for AI Adoption Without Disrupting Operations") Oct 14, 2025How-to Guides [ ### Preparing Your Team for AI Adoption Without Disrupting Operations ](/resource-center/preparing-team-for-ai-adoption) You need a structured approach that builds confidence without overwhelming people or disrupting the work that keeps your business running. FM Team FM [](/resource-center/the-roi-of-ai "Building Measurable ROI from Artificial Intelligence in 2025") Oct 5, 2025Thoughts [ ### Building Measurable ROI from Artificial Intelligence in 2025 ](/resource-center/the-roi-of-ai) In 2025, artificial intelligence has crossed a critical threshold. It's no longer experimental technology reserved for tech giants—it's an operational necessity for businesses of every size. FM Team FM [](/resource-center/identifying-automation-candidates "Identifying Which Processes Are Best Candidates for Automation") Oct 1, 2025How-to Guides [ ### Identifying Which Processes Are Best Candidates for Automation ](/resource-center/identifying-automation-candidates) Automate the right process first, and you'll demonstrate clear value quickly, creating appetite for more automation. Tim Visconti Co-founder @ FM [](/resource-center/from-prompt-to-product "From Prompt to Product") Sep 30, 2025Events [ ### From Prompt to Product ](/resource-center/from-prompt-to-product) Join us for a day of learning, networking, and hands-on experience with the latest tools and techniques for building digital products. FM Team FM [](/resource-center/trilith-studios-case-study "How Trilith Studios Empowered Their Team with AI: A Workshop Case Study") Sep 27, 2025Case Studies [ ### How Trilith Studios Empowered Their Team with AI: A Workshop Case Study ](/resource-center/trilith-studios-case-study) How FM's AI in Action workshop transformed Trilith Studios' team from AI novices to organizational thought leaders in just one day. Tim Visconti Co-founder [](/resource-center/forward-deployed-engineers "How Do Forward-Deployed Engineers Differ from Traditional Consultants?") Sep 16, 2025FAQs [ ### How Do Forward-Deployed Engineers Differ from Traditional Consultants? ](/resource-center/forward-deployed-engineers) Forward-deployed engineers work alongside your team to build solutions in real-time. The deliverable is solutions, not recommendations. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/how-to-choose-an-ai-consultancy "How to Choose an AI Consultancy: A Buyer's Framework") Sep 2, 2025FAQs [ ### How to Choose an AI Consultancy: A Buyer's Framework ](/resource-center/how-to-choose-an-ai-consultancy) A practical framework for evaluating AI consultancies: the dimensions that actually matter, the red flags to watch for, and the questions that reveal what kind of partner you're really hiring. FM Team FM [](/resource-center/what-makes-fm-different "FM vs. a Traditional Consultancy: An Honest Comparison") Aug 27, 2025FAQs [ ### FM vs. a Traditional Consultancy: An Honest Comparison ](/resource-center/what-makes-fm-different) An honest side-by-side comparison of FM and a traditional consultancy, including when a traditional firm is actually the better fit. FM Team FM [](/resource-center/custom-software-vs-saas "When Should a Growing Business Choose Custom Software Over SaaS Solutions?") Aug 19, 2025FAQs [ ### When Should a Growing Business Choose Custom Software Over SaaS Solutions? ](/resource-center/custom-software-vs-saas) As your business grows, you may outgrow SaaS platforms. Understanding when to build custom software can unlock competitive advantage. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/automation-without-job-elimination "Can Automation Reduce Operational Costs Without Eliminating Jobs?") Aug 5, 2025How-to Guides [ ### Can Automation Reduce Operational Costs Without Eliminating Jobs? ](/resource-center/automation-without-job-elimination) Automation typically augments teams rather than replacing them—and still delivers substantial cost reduction through avoided hiring and increased capacity. Tim Visconti Co-founder @ FM [](/resource-center/automation-vs-intelligent-automation "What's the Difference Between Automation and Intelligent Automation?") Jul 22, 2025FAQs [ ### What's the Difference Between Automation and Intelligent Automation? ](/resource-center/automation-vs-intelligent-automation) The difference matters because you'll invest very differently depending on which type your processes actually need. Tim Visconti Co-founder @ FM [](/resource-center/announcing-virtuosos-community "Announcing the Virtuosos Community") Jul 16, 2025Announcement [ ### Announcing the Virtuosos Community ](/resource-center/announcing-virtuosos-community) The Virtuosos community is a new community for product managers, UX designers, design professionals, and engineers who are ready to pioneer the future of how digital products are built. Brian Fletcher Principal / Co-founder @ FM [](/resource-center/ai-empowered-development-difference "What Makes AI-Empowered Development Different from Traditional Software Development?") Jul 8, 2025FAQs [ ### What Makes AI-Empowered Development Different from Traditional Software Development? ](/resource-center/ai-empowered-development-difference) AI has fundamentally changed how software gets built. If you're not leveraging it, you're competing at a significant disadvantage. Brian Fletcher Principal, Co-founder @ FM [](/resource-center/fm-virtuoso-series-no2 "Virtuoso Series: No. 2 - A Conversation with R Land") Jun 2, 2025Events [ ### Virtuoso Series: No. 2 - A Conversation with R Land ](/resource-center/fm-virtuoso-series-no2) For FM's second Virtuoso Series event, we are hosting a conversation with R Land about Art, AI, and Atlanta. FM Team FM [](/resource-center/ai-automation-advantage "AI Automation ROI: How Mid-Size Companies Save 40%+") May 16, 2025Thoughts [ ### AI Automation ROI: How Mid-Size Companies Save 40%+ ](/resource-center/ai-automation-advantage) Mid-size businesses are uniquely positioned to benefit from AI automation and drive meaningful transformation. FM Team FM [](/resource-center/your-business-your-software "Why Custom Software Beats SaaS for Growing Businesses") Feb 16, 2025Thoughts [ ### Why Custom Software Beats SaaS for Growing Businesses ](/resource-center/your-business-your-software) Discover how custom software solutions are transforming businesses and delivering competitive advantages. Brian Fletcher Principal / Co-founder @ FM [](/resource-center/fm-virtuoso-series "That's a Wrap...Our First Virtuoso Series") Feb 1, 2025Events [ ### That's a Wrap...Our First Virtuoso Series ](/resource-center/fm-virtuoso-series) Our launch event brought Virtuosos together to celebrate creativity. FM Team FM [](/resource-center/ebikes-and-copilots "e-Bikes and Co-pilots") Jan 19, 2025Thoughts [ ### e-Bikes and Co-pilots ](/resource-center/ebikes-and-copilots) FM Partner, Brian Fletcher, shares his thoughts on AI-empowered development. Brian Fletcher Principal / Co-founder @ FM ## Stay in the Loop Get the latest insights on AI, custom software, and business transformation. ## Ready to Build Something? We help companies figure out where AI fits, automate what should be automated, and build custom software that creates real leverage. [Let's Talk](/get-started)[Read About Us](/about-us) --- ## https://www.buildfm.com/contact-us Contact Us # Get In Touch Have a question or an idea? We'd love to hear from you. Reach Us Directly ## Other Ways to Connect Prefer to reach out directly? Here's how to find us. Email [hello@buildfm.com](mailto:hello@buildfm.com) Phone [+1 (404) 480-2787](tel:+14044802787) Address 1029 Peachtree Parkway N, Suite 204 Peachtree City, GA 30269 --- ## https://www.buildfm.com/get-started Start a Project # Let's Build Something Tell us about your project and we'll set up a discovery session with an FM Principal. How It Works ## What to Expect We'll review your submission and schedule a one-hour discovery session to understand your opportunity and explore how we can help. Email [hello@buildfm.com](mailto:hello@buildfm.com) Phone [+1 (404) 480-2787](tel:+14044802787) Still evaluating? Two reads that might help before you reach out: - [How to Choose an AI Consultancy](/resource-center/how-to-choose-an-ai-consultancy) - [FM vs. a Traditional Consultancy](/resource-center/what-makes-fm-different) --- ## https://www.buildfm.com/terms [Back to Home](/) # Terms & Conditions Last updated: February 16, 2025 ## 1\. Introduction Welcome to FM. By accessing our website or using our services, you agree to these terms and conditions. Please read them carefully before using our services. ## 2\. Services FM provides custom software development and consulting services. We reserve the right to modify, suspend, or discontinue any aspect of our services at any time. We may also impose limits on certain features or restrict access to parts or all of the services without notice or liability. ## 3\. Intellectual Property All content on this website, including but not limited to text, graphics, logos, images, and software, is the property of FM and is protected by copyright and other intellectual property laws. You may not use, reproduce, or distribute any content from this website without our express written permission. ## 4\. User Conduct When using our website or services, you agree not to: - Violate any applicable laws or regulations - Infringe on the rights of others - Attempt to gain unauthorized access to our systems - Transmit any harmful code or materials - Interfere with the proper functioning of our website ## 5\. Privacy Your privacy is important to us. Any personal information you provide through our website will be handled in accordance with our [Privacy Policy](/privacy-policy). By using our contact form or providing any personal information, you consent to our collection and use of this information as described in our [Privacy Policy](/privacy-policy). ## 6\. Limitation of Liability FM and its employees, officers, and representatives shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from your use of our services or any content provided on our website. ## 7\. Indemnification You agree to indemnify and hold FM harmless from any claims, damages, or expenses arising from your use of our services or any violation of these terms and conditions. ## 8\. Governing Law These terms and conditions shall be governed by and construed in accordance with the laws of the State of Georgia, United States, without regard to its conflict of law provisions. ## 9\. Changes to Terms We reserve the right to modify these terms and conditions at any time. Changes will be effective immediately upon posting to our website. Your continued use of our services after any changes indicates your acceptance of the modified terms. ## Contact Information If you have any questions about these Terms & Conditions, please contact us: FM 1029 Peachtree Parkway N, Suite 204 Peachtree City, GA 30269 [hello@buildfm.com](mailto:hello@buildfm.com) [+1 (404) 480-2787](tel:+14044802787) --- ## https://www.buildfm.com/privacy-policy [Back to Home](/) # Privacy Policy Last updated: February 16, 2025 ## Introduction At FM, we take your privacy seriously. This Privacy Policy describes how we collect, use, and protect your personal information when you use our website and services. ## Information We Collect ### Information You Provide - Email address when subscribing to our newsletter - Contact information when reaching out through our contact forms - Information shared during business inquiries and consultations ### Information Automatically Collected - Device and browser information - IP address and location data - Website usage data and analytics - Cookies and similar tracking technologies ## How We Use Your Information We use the collected information to: - Send you our newsletter and updates about FM - Respond to your inquiries and provide customer support - Improve our website and services - Comply with legal obligations - Prevent fraud and enhance security ## Information Sharing We do not sell, trade, or rent your personal information to third parties. We may share your information with: - Service providers who assist in our operations - Professional advisors and consultants - Law enforcement when required by law ## Newsletter Communications When you subscribe to our newsletter: - We collect only your email address - You can unsubscribe at any time using the link in our emails - We use Resend to manage our newsletter and your data is protected according to their privacy policy ## Data Security We implement appropriate technical and organizational measures to protect your personal information. However, no method of transmission over the internet is 100% secure. ## Your Rights You have the right to: - Access your personal information - Correct inaccurate data - Request deletion of your data - Withdraw consent for data processing - Object to data processing - Request data portability ## Changes to This Policy We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. ## Contact Us If you have any questions about this Privacy Policy, please contact us at: [hello@buildfm.com](mailto:hello@buildfm.com) --- ## https://www.buildfm.com/c/content-command-center # Your Content Team Is Drowning. AI Can Fix That. Your content operation wasn't designed for how marketing works now. The teams that redesign their workflows around AI will scale without adding headcount. The ones that don't will keep burning out trying to keep up. Schedule a Call Learn More The Problem ## The Content Bottleneck Is Costing You More Than You Think Every quarter, the asks get bigger. More campaigns. More channels. More personalization. More localization. Your team is already at capacity, and the backlog keeps growing. You've probably tried the usual fixes: more freelancers, more templates, more tools. But adding headcount doesn't scale, and most "AI tools" create more cleanup work than they save. When your team can't keep up with demand, the damage compounds: 01 ### Missed windows Campaigns launch late or not at all. Seasonal moments pass. Competitors move faster. 02 ### Inconsistent quality Rushed work means brand drift, messaging that doesn't land, creative that underperforms. 03 ### Burned-out teams Your best people spend their time on production treadmills instead of strategic work. Turnover follows. 04 ### Wasted spend You're paying for campaigns that don't get the content they need to perform. Media dollars go further when creative keeps pace. A Different Approach ## Why Most AI Content Fails (And How to Avoid It) You've probably seen the slop. Generic copy that sounds like everyone else's. Off-brand messaging that needs heavy editing. "AI-assisted" content that takes longer to fix than it would to write from scratch. That's what happens when you bolt AI onto broken processes. The tool isn't the problem. The workflow is. Our approach is different: ### AI handles volume, humans handle judgment We design systems where AI drafts, adapts, and scales content while your team sets direction, maintains brand standards, and approves output. ### Your brand, encoded We build guardrails into the workflow: tone guidelines, messaging frameworks, approval gates. AI operates within boundaries your team defines. ### Quality at speed, not quality or speed The goal isn't just more content. It's more content your team is proud to ship. What Actually Works ## Content Operations That Scale FM helps marketing organizations build content operations that scale without adding headcount. We call it a Content Command Center, but the name matters less than what it does: a redesigned workflow where AI handles the repetitive production work and your team focuses on strategy, creativity, and quality control. This isn't theory. Our clients typically see: 60-80% reduction in content creation time 100-300% increase in content output 25-35% decrease in production costs 20-40% increase in team productivity Same team. Dramatically more capacity. Why FM ### Built for real-world implementation #### We've done this before Our team has spent decades at the intersection of marketing and technology, leading transformations for organizations that actually shipped. #### We're not selling software We're technology-agnostic. We work with your existing stack and only recommend new tools when they'll genuinely help. #### We focus on adoption The best-designed system fails if your team doesn't use it. Change management is built into everything we do. #### We measure results Clear KPIs from day one. You'll know exactly what's working and what the investment is returning. Our Approach ## How We Get There 1 ### Discovery We map your current content workflows end-to-end. Where are the bottlenecks? Where is work getting stuck, duplicated, or dropped? 2 ### Design We architect a new operating model that integrates AI into your existing tools and processes. No rip-and-replace. 3 ### Build We implement the systems, train your teams, and establish the governance that keeps quality high as volume increases. 4 ### Optimize We measure what's working, refine what isn't, and help you scale further as your team gets comfortable with the new way of working. ## Is This Right For You? ### This approach makes sense if: - Your content team is at capacity and the backlog keeps growing - You've tried adding headcount or freelancers and it's not scaling - You're interested in AI but skeptical of the hype - You want to increase output without burning out your team ### This probably isn't right if: - You're a small team that doesn't have content volume problems yet - You're looking for a tool recommendation, not an operational transformation - You need results in 30 days (this work takes 2-4 months to do right) ## Let's Talk Schedule a 30-minute call to walk through your current content operation and see if there's a fit. No pitch deck. No pressure. Just a conversation about what's not working and what might. --- ## https://www.buildfm.com/c/own-your-platform # Stop Renting Your Learning Platform. Start Owning It. Off-the-shelf LMS platforms were built for their business model, not yours. The EdTech companies that own their platforms will integrate AI-native learning experiences, personalize at scale, and differentiate on product. The ones still renting commodity infrastructure will be competing with ChatGPT on price. Schedule a Call Learn More The Problem ## The Real Cost of "Good Enough" Systems You started with one tool. Maybe a simple LMS to host your courses. Then you added a payment processor. A marketing site on a different platform. A CRM that doesn't quite talk to anything else. Courses and SCORM files you created, bought or inherited. A spreadsheet to track what the systems can't. It worked well enough when you were small. But now every new initiative means another integration, another workaround, another manual process. Your team has become expert system wranglers, spending more time moving data between tools than actually improving the learning experience. And the worst part? You're paying for all of it. Monthly fees for six different platforms, none of which do exactly what you need, all of which lock you into their way of doing things. Every growth decision runs into the same wall: 01 ### Operational Drag Your team spends more time managing systems than serving learners. Manual data entry. Fragmented reporting. Workarounds that become permanent. 02 ### No Differentiation Your platform looks and feels like everyone else's because it is everyone else's. Your competitors have the same features because you're all renting the same software. 03 ### Trapped Data Customer insights scattered across platforms. No unified view of the learner journey. Decisions made on partial information. 04 ### Zero Flexibility When you need to pivot your business model, expand into new markets, or integrate AI capabilities, you're constrained by what your vendor decides to build. A Different Path Forward ## FM builds custom learning platforms designed around *your* business model We've done this before. An online education company came to us running their business across multiple disconnected systems. Strong business model, loyal customers, ready to scale nationally. But their team was drowning in operational inefficiency, manually stitching together tools that were never designed to work together. We replaced their fragmented stack with a single, purpose-built platform: ### End-to-end learner experience Marketing site, course delivery, assessments, certifications, and payments in one cohesive system. ### Admin tools designed for their workflow User management, tracking, and reporting built around how their team actually operates—not how a generic LMS thinks they should. ### Complete ownership They own the code, the data, and the roadmap. When they want to add AI-powered features, they can. When they want to expand into new markets, they can. No vendor approval required. The result: a platform that scales with their business instead of constraining it. The Urgency ## Why Now The window for platform ownership is narrowing. AI is fundamentally changing what learners expect and what's technically possible. Companies building on owned infrastructure today will be able to: ### Integrate AI where it matters Adaptive learning paths, intelligent assessments, AI tutoring—all built into your platform rather than bolted on. ### Own your learner data Train models on your unique dataset. Build proprietary insights your competitors can't access. ### Move faster than the market When the next disruption hits, you're not waiting for your vendor's roadmap. The EdTech companies still cobbling together commodity tools will be reacting. The ones with owned platforms will be leading. Our Approach ## How We Work 1 ### Discovery We analyze your current systems, map your operational workflows, and identify where you're bleeding efficiency. 2 ### Design We architect a platform built around your business model, not a generic template you'll adapt to. We rapidly prototype so you can see the vision. 3 ### Build Modern tech stack. Your team trained to maintain and extend it. 4 ### Launch and Beyond We can host, maintain, and continue developing your platform—or hand it off entirely. You own everything either way. ## Is This Right For You? ### This approach makes sense if: - You're running an EdTech business on stitched-together SaaS tools and SCORM files - Operational inefficiency is constraining growth - You need to differentiate on product, not just price - You want to integrate AI capabilities on your terms - You're ready to stop renting and start owning ### This probably isn't right if: - You're early-stage and still validating product-market fit - Your current tools genuinely serve your needs - You don't have budget for a real platform investment Click to expand Watch: Why ownership matters ## Ready to Talk? Schedule a 30-minute call to discuss your current stack, where you want to go, and whether a custom platform makes sense. --- ## https://www.buildfm.com/resource-center/software-that-takes-your-shape # Software That Takes Your Shape *Adapted from my talk at [RenderATL](https://renderatl.com), 13 August 2026. You can [watch the talk here](https://www.youtube.com/live/KFt5dAY9ZRw?si=Qespvmw3W611HPgS&t=22296) and poke at the [proof-of-concept on GitHub](https://github.com/BuildFM/render-conf-demo).* --- "It would take a new kind of model." I said that from a stage at SXSW in March 2024. The talk was about interfaces that stop being built in advance and start assembling themselves for whoever is standing in front of them, and I was sure about the shape of it. Composed at runtime. For one person. What I couldn't see was how you'd get there with the models we had, so I proposed we'd need a new class of them, trained on human-computer interaction the way language models are trained on text. I called it a Large Experience Model. I pointed at Rabbit's Large Action Model as the template to follow. Then I spent two years waiting for a model that never arrived. Nobody trained a Large Experience Model. Nobody needed to. The capability I said was missing turned up inside the models we already had, and when it did, the problem did not move an inch. I had it filed as a capability problem. It was never a capability problem. ## The one thing software has never done Look at the boots by my back door. A few hundred miles and they've taken the shape of my feet. A baseball glove takes the shape of one hand. A cookbook falls open to the page you actually cook from. The stone step in an old building has a dip worn in the middle where everyone walks. Everything we own gets more personal the longer we use it. Software doesn't. The application you've opened every morning for three years is identical to the one a stranger opens for the first time this afternoon. All that use went somewhere, and it did not go into the product. It went into you. You learned where things live, you built the workarounds, you memorised which of the seven tabs has the thing you actually need, and you stopped noticing the four features you've never once opened. You did the conforming. The software has your data. It doesn't have your shape. That's the whole reason to care about any of this. An interface composed for you, in the moment you ask for it, is not a gimmick. For the first time, the adaptation runs the other way. The software takes your shape instead of you taking its. This is the killer use case for a real-time UI. Software that evolves toward the person using it, the longer they use it. ## What a real-time UI actually is A real-time UI is a user interface a large language model renders in real time, in the moment you ask for it. When you open the app, a model decides which components appear on the page, in what order, at what depth, and what gets computed across them. It decides right then, for you. Nobody drew that page. Nobody has ever seen it. It didn't exist until you asked for it. Every piece it was built from was designed by a person, in advance and on purpose. Start with why the design matters at all, because it's easy to wave past. Put a recipe on a page as a paragraph of prose. Ingredients, times, method, all of it, perfectly accurate. Now put the same recipe in a card, with the photograph and the total time and the rating sitting where your eye already expects them. Same information. One of them you read in a second. That card is doing more work for a person than the words in it ever will, and shaping how people meet information is the thing we are all actually in the business of. So interfaces matter. The design is the product, not decoration laid over it. And brand matters just as much, because the second an interface stops looking like it came from you, people quietly stop trusting that it did. A word for the designers, because this is where a lot of you have quietly checked out. The story you keep getting handed is that all of it ends in a chat box. Brand flattened into sameness, experience templatized, craft turned into something a machine does cheaply and badly while you watch from the side. I think that story is backwards. If the design is the product, and the model can only ever work inside what you define, then you are not being pushed to the margins. You become the thing everything else has to run through. This is the opening to matter more, not less. For thirty years it has been fixed. Somebody designed the screen once, and everybody got that screen. Personalization was supposed to soften that. It didn't, and not because anyone did it badly. Personalization only ever decides *which of these* you get. A generated interface decides *what this should be*. One picks from a menu somebody wrote in advance. The other composes. The difference that matters most is subtraction. Recommendation engines almost never take anything away, because removing something risks removing the thing you wanted, and there's no signal safe enough to justify the gamble. So products accrete. Every feature anyone might need stays on the screen forever, and the interface you use in year three is the one built for the person you were in week one. For somebody two years into a product, the single most valuable thing it could do is stop showing them what they've already decided about. Adding is easy, and it's what we've all been doing. Taking away requires knowing something. Models can work in layout now, not only in words. That means the experience itself can finally be the thing that adapts, built from components you already designed, so it still comes out looking like your product. So here's the honest question I put to a room of designers in Atlanta: would you let it do that live, unattended, in front of real users? ## Why it's suddenly possible Ask a frontier model to build you an interface today and it will. It'll be plausible, it'll run, and it will not be yours. Wrong type. Wrong spacing. Some button with a gradient on it that's never appeared anywhere in your product. For a company that's spent years and real money making sure a hundred screens all come from the same place, plausible is not a passing grade. It's a liability with a login. While I was waiting, everybody else solved this from the other end. Shopify shipped [MCP-UI](https://shopify.engineering/mcp-ui-breaking-the-text-wall). Anthropic standardised the same idea as [MCP Apps](https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/). Google's [A2UI](https://a2ui.org/) sends only the name of a component and lets your client render it. Salesforce shipped a [generative canvas](https://bigmedium.com/ideas/links/salesforce-generative-canvas.html) that assembles CRM dashboards on the fly and doesn't come out a hallucinated mess, because it can only select from their own design system. Groups with nothing in common, arriving at the same answer without coordinating, which usually means the shape of the problem forced it rather than that anyone was clever. Not one of them lets the model draw. Every single one has it picking from components a human approved in advance. The designer [Josh Clark](https://bigmedium.com/ideas/when-interfaces-draw-themselves.html) puts it better than I would: the model supplies the adaptivity, the design system supplies the consistency, and neither one works without the other. So the work isn't in the model. It's in what you hand it. You define what's allowed: when a component may appear, what must always appear and where, what has to stay together. The model decides only which pieces, for this person, right now. An allergen warning sits immediately above the dish it's about, and no model anywhere gets a vote on that. A comparison table only shows up when there are genuinely three things worth comparing. You set the conditions. You don't build the outcome. Then code checks the model's work every single time. That last reframe is the one I didn't see coming. For fifteen years we sold design systems on efficiency: consistency, velocity, fewer arguments about button radii. And every one I've ever seen funded that way became the thing nobody wanted to own, maintained out of duty by whoever drew the short straw. We were quietly building the substrate for this the whole time. The ceiling on what a model can safely do inside your product is set by how well you've written down what your components mean. That is a limit you control. ## So I built it Theory is cheap. I wanted to know whether any of this survives contact with something real, so I built a recipe site called Mise and gave it a deliberately loud brand, the kind that goes obviously wrong the moment something off-key lands on the page. Two rules carry the entire build. The model never draws anything, and what it picks from is one file I wrote. Two of the households in the demo filled in byte-identical signup forms. Same size, same diet, same stated skill, the same nine things in the pantry. Their pages have almost nothing in common, because the form is not what the system is reading. It's reading what each person has actually cooked. A third household gets a page with no recipe on it at all. That one is a learner ninety days in, who abandons long ingredient lists and has never repeated a dish. A strange thing for a recipe site to decide, and exactly the right thing for someone who needs the technique rather than another dish. On stage I struck one component out of that file, saved it, and both pages rebuilt around the absence in about ten seconds. Nobody had written a template for what to do without it. Three things surprised me, and I predicted none of them. It looked designed, not generated. The model turned out to be the smallest part of the system: eight of the ten steps that build a page never touch a model at all. And it costs cents a page. ## What I still don't know A fixed component set is not a guarantee of correctness, and this is the objection I take most seriously. The engineers at Shopify make the case better than I can. Commerce UI is deceptively complex. Dependent variants, bundle pricing, inventory that moves while you're looking at it. A model can assemble a product card out of nothing but approved components and still be wrong, because the constraint does not live in the components. It lives in the relationships between them. Valid parts, invalid whole. My assemblies are the shape of an answer to that. They are not a proof, and a recipe site is not the hard case. The other gap is data, and it's the one that will actually stop you. Analytics knows what a crowd did. This needs what one person did, and the difference between somebody glancing at a recipe and somebody actually cooking it on a Tuesday is not sitting in your warehouse. You have to build a product that can tell those two apart, and keep what it learns. Almost nobody has. I think that's the real work item hiding behind all of this, and it's a bigger one than the design system. ## The web is ours to make Picture it a few months in. The recipe app opens straight to tonight's dinner. The training plan routes around the knee you hurt in March. The tool you're learning on has folded away the parts you've already mastered and left the one thing you're still fumbling. Nobody set a preference. Nothing asked. The software just took the shape of the person using it. None of that is waiting on a breakthrough. The web became the web because a generation of makers took a pile of raw technology and refused to leave it as plumbing. A markup language. A scripting hack. A way to shuttle data around. They built the storefronts and the feeds and the maps and the tools, the whole living thing we now spend our days inside. Every good part of it started with someone deciding the primitives were an invitation, not a limit. We've just been handed a new one. Interfaces that compose themselves, for one person, in real time. Software that finally adapts to us instead of us to it. It's sitting there right now, in the models you already have and the components you already own, waiting for someone to build with it. That's the opportunity in front of us. Not a faster chatbot. A web that takes the shape of the people who use it. Go make that. The proof-of-concept is linked up top. Go break it, and let's talk. --- ## https://www.buildfm.com/resource-center/announcing-fm-labs # Announcing FM Labs ## From 631 Clicks a Day to Under 100 One operator was clicking 631 times a day to get through their work. Today it's under 100. That's an 84% reduction, and it came out of an engagement FM ran for a client. The software was custom. The thinking behind it wasn't. How to spot the repetitive work. How to hand the mechanical part to an agent. How to keep a person in the loop where judgment actually matters. That part is teachable, and we have been teaching it. Today we're making it official. [FM Labs](https://labs.buildfm.com/) is live. ## What FM Labs Is > FM Labs teaches individuals how to use AI in their own work. One person, one real problem, one working tool at the end of it. Ryan, an early-stage founder who came through a session, built an image recognition workflow for his daily inventory count. It used to take three hours. It now takes five minutes. That's the product. Not a certification. Not a theory dump. Not a webinar you half-watch while clearing your inbox. You bring a problem from your actual job, and you leave with something that runs. ## Six Months, A Thousand People I've been running these sessions in the open for six months. Where it stands: - 120+ sessions, all free - 1,000+ attendees - 110+ automations built by attendees, in the room Sessions run every week in Peachtree City. Beginners on Wednesdays, more advanced builders on Fridays. One hour, hands-on the whole way, capped at 25 people so it stays a workshop instead of turning into a webinar. ## Why It's Free Because we already did the work, and somebody else already paid for it. FM builds custom software and AI agents for businesses. Every engagement teaches us something specific: which patterns hold up under real volume, which ones quietly fall apart, where an agent can be trusted to run unattended, and where a human has to stay in the loop or the whole thing goes sideways. That knowledge has been tested against real money and real consequences. Publishing it costs us very little. It's worth a great deal to somebody trying to work it out alone on a Saturday. So the workshops are free, and the material in them is not watered down. It's the same thinking we bring to paid client work, vetted by businesses, handed to whoever shows up. ## The Library The workshops aren't the only free thing. FM Labs publishes prompt frameworks, tool breakdowns, and walkthroughs for applying AI to specific business problems. Same source, same standard: written by people who do this work for paying clients every week. You don't have to wait for a Wednesday. [Browse the library](https://labs.buildfm.com/resources) and start today. ## Where Labs Ends and FM Begins This line matters, so I want to be plain about it. **FM Labs is for individuals.** A founder, an owner, a manager, a team lead, anybody who wants to be better at this. The engagement is with you and the work in front of you. **FM is for companies.** If you want your whole team trained, your operations rebuilt, or custom software that becomes part of how your business runs, that is a different problem and it needs a different engagement. That's [FM](https://www.buildfm.com/get-started). ## Going Deeper Than a Workshop For people who want more than the free hour, we work one on one. Since late April, five business owners have gone through it. Each is getting back three to four hours a week. Small numbers, deliberately. We would rather report five people we actually measured than a number we projected. At company scale the ceiling looks different. Through agent-operated leadership work, we returned 52 hours a month to [ProCivica](/resource-center/procivica-case-study). That's what an organization gets when it commits. Three to four hours a week is what one person can start reclaiming now, without a budget cycle or anybody's approval. ## Why We Do This In Person The numbers are the easy part to write down. The part I care about is harder to count. We ran a day of training with the team at [Trilith Studios](https://www.trilithstudios.com), and we did the same with [GSU Perimeter College](https://perimeter.gsu.edu). Two very different rooms. The same thing happened in both. People walk in braced for a lecture about the technology that's coming for their job, then somewhere in the middle they build something that actually works, and you can watch the room change its mind. AI stops being a threat and turns into a tool they own. That shift is hard to manufacture over video. It needs a room, and somebody sitting next to you when the thing breaks on the first try. It's why sessions are capped at 25 and why we've kept them free. We've also been hitting that cap, which is a good problem to have. Online courses are coming so more people can get to the material, though I'll say plainly that the room is still the best version of this. Where FM Labs goes next depends mostly on who shows up. That's how the last six months went, and it worked out better than I expected. ## Start [Find a workshop.](https://labs.buildfm.com/workshops) They're free, and they cap at 25, so they fill. Want to work with us directly? [Book a call.](https://labs.buildfm.com/contact) Leading a team and want this for all of them? [Talk to FM.](https://www.buildfm.com/get-started) --- ## https://www.buildfm.com/resource-center/ai-persona-tool-case-study # From Generic GPT to Proprietary AI Asset: An AI Persona Tool Case Study **A three-month build that turned an agency's tactical workflow problem into a productized, proprietary AI asset.** ## The Situation A tech-forward creative agency had been using off-the-shelf custom GPTs to simulate customer focus groups for one of their largest enterprise clients—a Fortune 500 automotive brand running a high-traffic peer-to-peer marketplace. On paper, this was a smart workflow. Run a concept past a synthetic audience before spending real research budget to test it with real customers. In practice, it kept breaking down on the same two failure modes. **The first was sycophancy.** Generic LLMs are trained to be helpful and agreeable, which means they tend to praise whatever idea is put in front of them. For an agency trying to stress-test creative concepts, that's the opposite of what's useful. You don't need an AI that tells you your work is good. You need one that tells you where it's weak. **The second was missing audience nuance.** Public LLMs had no access to the agency's first-party research, no access to their licensed audience insight reports, and no memory of historical content performance. The "personas" they simulated were stereotypes pulled from training data, not the actual modeled audiences the agency had spent years understanding. The agency came to FM with a clear ask: build a proprietary AI persona tool that defeats sycophancy, grounds itself in real research, and—critically—is an asset they own rather than a third-party product they rent. They wanted to walk away from the engagement with software they could extend, deploy across their book of business, and use as a strategic differentiator against other agencies. ## The Approach FM staffed the engagement with a small senior team and ran it as a three-month build. The technology stack was deliberately chosen for AI-native workloads and long-term maintainability: **Next.js and React** on the frontend, **the Vercel AI SDK** for LLM orchestration against OpenAI's frontier models, **Neon Postgres with pgvector** for the retrieval layer, **PostHog** for analytics, and **Vercel** for hosting. But the technology was the easy part. The hard part—and the part the agency was actually paying for—was the AI engineering. ## Defeating Sycophancy by Design Sycophancy isn't a bug you fix with a single clever instruction. It's a default behavior baked into how LLMs are trained, and it has to be engineered around at multiple layers. So FM didn't try to solve it with one prompt—the persona system was built as a layered architecture, where each layer pushes the model further away from generic agreeability: - A **"Research Lead" system prompt layer** that frames every interaction as a structured research exercise rather than a creative brainstorm, orienting the model toward critical evaluation rather than encouragement - A **"Master Tone of Voice"** layer that defines how every persona communicates—skeptical, direct, grounded in their own perspective—regardless of who's behind the keyboard - **"Anti-Sycophancy" guardrails** that explicitly prevent the model from parroting the user's input back at them or copying example content verbatim - A **structured persona model** (covered below) that gives the AI a real point of view to reason from, rather than defaulting to an agreeable generic baseline The result is a tool that disagrees, pushes back, and surfaces weakness—the things a strategist actually needs from a "first filter" before live customer testing. ## Personas That Reason from Mindset, Not Stereotype The second core problem was the persona model itself. Most "AI persona" tools are little more than demographic templates with a prompt. FM designed something deeper. Every persona in the tool is built on a **four-pillar framework**: Demographics, Psychographics, Behavioral Data, and Response Guidelines. And critically, the weighting between those pillars is calibrated to reflect how real audiences actually behave. **Psychographics carry 40% of the weight. Behavioral data carries significant weight. Demographics carry just 10%.** That weighting matters. It forces the model to reason from *mindset*—motivations, attitudes, decision-making patterns—rather than from *age and zip code*. The flagship persona built on this framework was a high-fidelity model of 25- to 41-year-old private vehicle sellers, the exact audience the agency's enterprise client needed to reach with their peer-to-peer marketplace. ## Grounded in Real Research, Not Model Imagination A persona is only as good as the data behind it. So FM built a **Retrieval-Augmented Generation (RAG)** pipeline on Neon Postgres with pgvector that ingests the agency's actual research documents and licensed audience insight reports. When a strategist asks a persona to react to a creative concept, the system retrieves the relevant research, grounds the persona's response in actual data, and—this part matters—**shows the strategist exactly which documents the AI referenced**. Source transparency is what makes the tool trustworthy for high-stakes strategic decisions. It's the difference between "the AI said this" and "the AI said this, and here's the research it pulled from." For an agency selling strategic rigor to enterprise clients, that distinction is non-negotiable. ## A UI Built Around How Strategists Actually Work The first version of the persona builder was a rigid, form-driven data entry experience. It was clean and well-structured, and it didn't match how the agency's strategists actually thought about persona construction. FM watched the team work, threw out the form, and rebuilt the experience around a **three-tab structure**: Demographics & Psychographics, System Prompts, and Tone of Voice. The new UI mirrored the strategists' actual mental model—building a persona is a craft, not a data entry task—and adoption inside the agency followed immediately. The full application includes: - **Interactive chat** for real-time evaluation of text and image-based creative - A **searchable knowledge base** of uploaded research documents - An **admin dashboard** with persona management, document tagging, and full version history with rollback - **Source transparency** built into every persona response ## Multi-Tenant from Day One The agency's ambition wasn't just to solve the problem for one client. They wanted a platform they could deploy across their broader portfolio. FM designed the database, authentication, and access model to be **multi-tenant from the first commit**, with three tiers of access (User, Admin, Super Admin) and clean separation between clients. The Fortune 500 automotive brand was the first deployment. Additional enterprise clients have been onboarded onto the same infrastructure since. That decision—designing the platform as a product rather than a one-off—is why the agency now has an asset they can sell against, not just a tool that solves one workflow. ## Compound Engineering for Velocity A three-month build for a proprietary AI persona platform with a custom RAG pipeline, multi-tenant infrastructure, and a full admin experience is aggressive by any measure. FM hit the timeline by leaning hard on **compound engineering**—automated workflows powered by Claude and MCP that collapse 4+ hours of manual strategy and prompt-engineering work per cycle into parallelized AI sessions. Human-in-the-loop direction on architecture, AI velocity on implementation. Same model FM uses on every senior-team build. ## The Result The platform shipped **on schedule, with final client approval, and zero post-handoff revisions requested**. What got delivered: - **A proprietary AI persona platform** built on Next.js, Vercel AI SDK, Neon Postgres + pgvector, and PostHog - **A high-fidelity flagship persona** modeling the agency's enterprise client's most strategically important audience segment - **A multi-tenant infrastructure** that now serves multiple enterprise clients, with more being onboarded - **A complete infrastructure handoff**: Vercel hosting, GitHub repositories, and PostHog analytics fully migrated from FM's environment to the agency's internal stack - **Technical documentation** for the agency's IT team to maintain and extend the platform long-term Strategists can now iterate on creative concepts in minutes rather than waiting for traditional research cycles. The tool functions as a "first filter"—catching weak concepts before they consume live research budget and putting the strongest work in front of real customers. And the agency walked away owning the asset, not renting it. ## Why It Worked **Layered engineering against the core LLM weakness.** Most "AI persona" tools are a single prompt and a clever UI. FM engineered the persona system at multiple layers—system prompts, tone-of-voice, anti-sycophancy guardrails, and a structured persona model—because sycophancy can't be solved with a single instruction. **RAG grounding with source transparency.** Trust is what makes AI output usable for strategic decisions. Showing the receipts is how you earn it. **Calibrated weighting that prioritized mindset over demographics.** Personas reasoned from psychographics and behavior, not from stereotype. **A UI built around the strategist's workflow.** The form-driven first cut got thrown out. The three-tab structure matched how the team actually worked—and adoption followed. **Multi-tenant from day one.** The agency didn't pay for a one-off. They got a platform they could productize. **A clean infrastructure handoff.** The agency owns the code, the database, the analytics, and the deployment pipeline. No vendor lock-in to FM. That's the model. ## For Agencies Considering Their Own AI Platform If you're an agency still renting capability from third-party AI tools, this is what's possible when you invest in building your own. You don't need a fully staffed in-house AI team. You don't need a year-long roadmap. You need a senior team that understands both the engineering and the strategic problem you're trying to solve, and a willingness to build something defensible rather than buying something generic. **That's what FM builds for.** --- ## Ready to Build Your Own? If you're ready to stop renting AI capability and start owning a proprietary AI asset, FM can help you ship a production-grade platform on a timeline you'll actually hit. **[Get Started](/get-started)** or **[Learn More About Our Work](/expertise)** --- ## https://www.buildfm.com/resource-center/31-day-replatform-case-study # From Kickoff to Launch in 31 Days: The AnswerLab Replatform **A full design, build, and CMS replatform—shipped in 31 days, one day ahead of a hard deadline.** ## The Situation [AnswerLab](https://www.answerlab.com)—a leading UX research firm trusted by some of the biggest brands in the world—had a problem that will sound familiar to a lot of services companies: their marketing website no longer matched their reputation. Built on an aging HubSpot instance, the site felt antiquated. It lacked the performance, the motion, and the dynamic presence you'd expect from a company whose entire business is understanding great user experiences. They needed a full replatform: new design, new technology, new CMS. And this wasn't a "when you get around to it" project. The deadline was non-negotiable. Critical banker meetings were on the calendar, and AnswerLab was sponsoring a major industry event weeks later. The new site had to be live, polished, and representing the brand at its best. On top of the timeline pressure, AnswerLab had a massive content library—**192 insights articles and 58 case studies**—that needed to be preserved and migrated. This wasn't a greenfield build. It was a full replatform with real content at stake. AnswerLab came to FM with useful starting assets: a clearly articulated set of brand guidelines and wireframes from a previous agency. What they needed was a team that could take those inputs and ship a production website in roughly five weeks. ## The Approach FM assigned a two-person core team to the build: one senior designer and one senior developer. The technology stack was modern and deliberately chosen for speed and long-term maintainability: **Payload CMS** for content management, **React and Next.js** for the frontend, **Tailwind CSS** for styling, and **Vercel** for hosting, where performance is a first-class citizen via a global CDN. Development was Claude Code–accelerated, supported by a library of custom skills and plugins that FM actively maintains to keep output quality consistently high. Then came the first unconventional decision, and the biggest one: **FM skipped Figma.** Rather than spending weeks cycling through static design comps, the team collapsed design and development into a single parallel workflow. On day one, the developer converted the full set of wireframes into a clickable prototype, working entirely in code. Not a throwaway prototype in a design tool—the actual beginnings of the production site. While the developer was building structure, the designer was deep in the brand guidelines, absorbing the visual language, the philosophy, and the intent behind every decision. Then the two of them started working together in real time. The designer directed the visual design while the developer implemented it live, in the browser, on the actual codebase. No handoff. No redlines. No "developer interpretation" of a static comp. **The design was born in the medium it would live in.** For the designer, this was a first. The experience changed his perspective on what's possible when design and engineering move as a single unit rather than a sequential pipeline. **Four days after kickoff, FM had a working homepage prototype.** Not a wireframe. Not a mood board. A live, responsive page with the brand fully realized, rich motion design, and a complete component library—ready for client review. ## A Living Brand Experience AnswerLab had a clear vision for what the site should feel like. They described it as a "living brand experience" built on "intentional storytelling through motion." The animation language was guided by a central concept: things coming together—a visual metaphor that resonated deeply with their core brand story. FM leaned into it. The site is motion-forward, with fluid, tactile interactions that give the experience a sense of life and intentionality. Navigation was simplified, removing complex dropdowns in favor of letting the pages themselves do the explanatory work. A significant design pivot happened mid-project. AnswerLab's design lead pushed for a typography-forward direction, advocating to treat copy as a design element rather than filling space with imagery. CEO Megan Malli reinforced this by making the executive call to **eliminate all stock photography** from the site for the MVP launch. The team would rely on high-end typography and authentic team photos to reflect the brand's maturity and credibility. It was a bold move on a tight timeline, and it made the site stronger. The result feels honest and confident in a way that stock-photo-heavy B2B sites rarely do. ## The Rhythm FM established a weekly demo cadence. Each week, the team would design and build multiple new sections of the site using the same collapsed workflow, then present the progress live. After the second demo, AnswerLab's CMO noted that the velocity between the first two check-ins had already exceeded expectations—validating the choice of a headless architecture and AI-augmented workflow for speed. AnswerLab's feedback was incorporated in near real-time, keeping the project tight and aligned without the overhead of lengthy review cycles. Behind the scenes, FM was simultaneously handling the less visible but equally critical work: - Technical due diligence on the hosting environment - Security review with AnswerLab's internal security team - Infrastructure procurement - A 301 redirect strategy for **over 250 migrated content assets** - Integrations with HubSpot (direct API for forms), BambooHR, PostHog, and Demandbase One small but telling detail: FM built an auto-redirect system directly into Payload CMS that automatically disables a redirect once the corresponding article is published. It's the kind of operational refinement that saves hours of manual work over time—and signals that FM was thinking about long-term maintenance, not just hitting a launch date. ## The Hard Part Nobody Talks About Around the midpoint, the team hit what you could call **perfection paralysis**. With the site coming together so quickly and looking so good, there was a natural temptation to keep polishing—to push every page to its final state before launch. A mid-project check-in became the critical alignment moment. The team collectively agreed that the site could iterate post-launch, and that hitting the hard deadline with a strong MVP was more important than shipping perfection on day one. This is a lesson that matters for any B2B services company considering a replatform: **the willingness to ship, learn, and iterate is what separates teams that launch from teams that stay stuck in revision cycles.** ## The Result The site went live **one day ahead of the critical banker meeting deadline**. By the numbers: - **Kickoff to MVP: 31 days** - **Prototype lead time: 4 days** - **Content migrated: 400+ assets** - **Tech stack:** Payload CMS, Next.js, Vercel, Tailwind CSS - **Integrations:** HubSpot (Direct API), BambooHR, PostHog, Demandbase The full Payload CMS was stood up and functional at launch—something FM had originally scoped as a future phase. Subsequent phases focused on refining the CMS authoring and publishing workflow, full CMS training for the AnswerLab team, the careers page integration with BambooHR, and continued content migration. ## Why It Worked **A collapsed design-development workflow.** By eliminating the traditional handoff between design and engineering, FM removed the single biggest source of delay and fidelity loss in web projects. The designer and developer worked as a unit, making decisions together in the medium that mattered: the live product. **AI-augmented development.** Claude Code, backed by FM's maintained library of custom skills and plugins, dramatically accelerated the build without sacrificing quality. This isn't about generating throwaway code. It's about a senior developer using AI tooling to operate at a pace that would otherwise require a much larger team. **A senior team model.** FM doesn't staff projects with layers of junior resources overseen by a single senior lead. Both team members were senior practitioners. No ramp-up time, no quality gap to manage, and no communication overhead from a bloated team structure. Two experienced people, working in lockstep, moved faster than a team of ten. **A client willing to move.** AnswerLab's leadership made fast, decisive calls throughout the project—the stock photography pivot, the navigation simplification, the agreement to ship an MVP and iterate. These decisions kept the project on track. Speed is a two-way street, and they held up their end. ## For B2B Services Companies Considering a Replatform If your marketing website is stuck on a platform that's holding you back—whether that's HubSpot, WordPress, or something else entirely—this is what's possible when you work with a team built for speed and quality. You don't need a six-month engagement. You don't need a 30-slide strategy deck before anyone writes a line of code. You need a small, senior team with the right tools and the right process, and a willingness to move at the pace the work actually demands. **That's what FM builds for.** --- ## In the Client's Words > Brian Fletcher and the FM team were exceptional partners during AnswerLab's website rebuild and brand relaunch. Beyond delivering a beautiful end product, what impressed us most was how strategically and innovatively they leveraged technology to completely transform the way we worked together. > > Brian is building something truly differentiated at FM — combining strong creative and brand thinking with modern tooling and workflows that enabled real-time iteration, rapid decision-making, and an incredibly efficient execution process. Their use of technology allowed us to collaborate dynamically on designs, content, and development in ways that dramatically accelerated the project without sacrificing quality. > > One of the most remarkable outcomes was their ability to help us launch the initial version of our new site in just four weeks. That speed would not have been possible without the systems, responsiveness, and operational excellence Brian and his team have built into their process. > > Throughout the engagement, the team felt like a true extension of ours: highly strategic, deeply responsive, thoughtful in every interaction, and committed to delivering exceptional work. Their customer service and turnaround time were outstanding, and they consistently brought smart solutions and fresh thinking to the table. We're incredibly proud of what we launched together and grateful to have had FM as a partner through such an important brand milestone. > > — **Megan Malli**, CEO, AnswerLab --- ## Ready to Replatform? If you're ready to move off a platform that's holding your brand back, FM can help you ship a modern, motion-forward marketing site on a timeline you'll actually hit. **[Get Started](/get-started)** or **[Learn More About Our Work](/expertise)** --- ## https://www.buildfm.com/resource-center/saas-leak # The SaaS Leak: Why Operations are Moving from Fixed Subscriptions to Disposable Leverage ## The Rise of the SaaS Leak At a [recent roundtable](https://www.akashbajwa.co/p/the-future-of-software-engineering) hosted by Anthropic and Balderton Capital, a group of practitioners shared a trend that should make every SaaS founder uncomfortable. They weren't just using AI to write code faster; they were using it to systematically dismantle their third-party software stack. Teams are beginning to rip out established "point solutions"—tools for incident management, auth, project tracking, and customer triage—and replacing them with custom versions built in a single weekend. We call this the **"SaaS Leak."** For a decade, the operational mandate was: *Buy whenever possible; build only if it’s your core product.* That was sound advice when a simple internal tool required a six-month roadmap and a dedicated squad. But in the age of Claude Code and agentic engineering, the friction of "building" has vanished, while the friction of "generic SaaS" has become a bottleneck. The SaaS Leak happens when a company realizes that their expensive, 500-feature software subscription is actually making their team work harder just to fit into a "standard" workflow. ## The Problem with "Generic" Excellence Most SaaS companies win by being "good enough" for the widest possible audience. They build for the "average" company. But your competitive advantage doesn't live in the average parts of your business; it lives in the quirks, the specific logic, and the unique way your team handles a crisis or a customer. When you use a generic tool for a specific operational workflow, you pay two prices: 1. **The Subscription Tax:** The literal monthly cost per seat. 2. **The Workflow Tax:** The time your team spends "working around" the tool—manual data entry, clicking through ten screens to do one task, or exporting data to Excel because the tool’s reporting doesn't quite fit. The SaaS Leak is the process of reclaiming that "Workflow Tax." ## From Permanent Assets to Disposable Tools In our [previous analysis of Build vs. Buy](/resource-center/build-vs-buy-agent-age), we argued that companies should build "Force Multipliers" and buy "Systems of Record." The SaaS Leak takes this a step further by introducing the concept of **Disposable Software.** Traditionally, "Custom Software" meant a multi-year commitment. You built it, you maintained it, you upgraded it. It was a heavy asset. Today, if a senior engineer can prompt a functional triage bot or a custom incident dashboard into existence in four hours for $12 in tokens, that software doesn't need to live forever to be "worth it." If it solves a bottleneck for six months and then becomes obsolete because your process evolved, you haven't lost a $100k implementation fee. You just turn it off and build the next iteration. **Software is moving from an "Asset" mindset to a "Utility" mindset.** You don't buy a permanent shovel; you 3D-print the exact tool you need for the hole you're digging today. ## Where to Let the Leak Happen To manage the SaaS Leak effectively, you need to know which parts of your stack should remain "Fixed" and which should be "Fluid." ### 1. The Fixed Basement (Systems of Record) Do not build your own basement. These are the tools where the value is in the ecosystem, the security, and the data integrity. * **Keep Buying:** Gusto, Salesforce, Stripe, Slack. * **Why:** You aren't building a competitive advantage by having a custom payroll engine. You’re just inheriting a massive compliance headache. ### 2. The Fluid Layer (Connective Tissue) This is where the leak provides the most leverage. Look for the "gaps" between your big platforms. * **Example: The Triage Engine.** Instead of an expensive AI Support Platform, build a custom agent that sits between your shared inbox and your CRM. It categorizes tickets based on your *actual* historical data, not generic intent models, and drafts responses that follow your specific brand voice. * **Example: The Decision Harness.** If your team spends 10 hours a week in spreadsheets trying to decide which inventory to buy, build a tool that pulls from your ERP and runs your specific proprietary logic. ## The New "Build" Criteria When deciding whether to "leak" a SaaS tool into a custom build, ask three questions: 1. **Does the SaaS tool force us to change our process to fit its UI?** If yes, build. 2. **Is the "maintenance" of a custom version just logic updates, or is it infrastructure?** If it’s infrastructure (security, hosting, compliance), keep buying. If it’s just logic (how we categorize a lead), build. 3. **Can we ship a 'v1' that provides value in under 48 hours?** With modern agentic tools, if you can't see a working version in a weekend, you're over-engineering it. ## The Operational Intelligence Era The goal of the SaaS Leak isn't to save money on subscriptions (though your CFO will be happy). The goal is **Operational Intelligence.** When you own the "Connective Tissue" of your business, you own the data and the logic that makes you fast. You stop being a "Salesforce Shop" or a "Zendesk Shop" and you start being a company that uses custom intelligence to move faster than the competition. The era of "one-size-fits-all" software is ending. It’s time to start building the 10% of code that gives you 90% of the leverage. --- *At FM, we help operational leaders identify high-leverage opportunities and build the custom tools that power them. If you’re tired of your team working around your software instead of with it, [let's talk](/get-started).* --- ## https://www.buildfm.com/resource-center/good-enough-is-not-enough # Good Enough Is Not Enough # The “Good Enough” Market Just Flooded. It’s Time for the Precision Standard. Eighteen months ago, a "passable" digital product was a legitimate business asset. If you could ship a functional dashboard, a clean landing page, or a stable API, you had a career. That skill set was a moat. The barrier to entry kept the noise out. That barrier is gone. Welcome to the Great Leveling. Anyone with a browser and a prompt can now generate 7/10 work in seconds. The middle of the market — where "good enough" engineers and designers used to thrive — is drowning in what we call **AI Slop**: code that compiles, copy that reads, designs that render. All of it hollow. If your work looks like something a machine could produce in one pass, you aren't competing with other humans anymore. You’re competing with a script that costs $20 a month and never sleeps. The middle is underwater. The only move is up: the **Precision Standard.** ## The Lethal Cost of “Good Enough” Most professionals assume "good enough" is still a safe place while they "figure out AI." It isn't. Staying in the middle carries three costs, and each one is terminal. ### 1. The Commodity Trap When a task moves from "hard human effort" to "instant AI output," the market price for that task collapses. If a founder can prompt their way to a functional MVP over a weekend, they aren't going to pay a professional for "functional." The 7/10 developer is now a commodity, and in commodity markets the only differentiator is price. Unless you want to join the global race to the bottom on hourly rates, you have to deliver the 3/10 that AI can't touch: the judgment, the nuance, and the obsessive polish. ### 2. The “Slop” Signal Users can already smell AI-generated beige. Generic UX patterns, repetitive copy, unpolished edges. They all send the same subconscious signal: *The people who built this didn’t care.* When low-effort content is infinite, **intentionality is the only remaining signal of quality.** A perfectly timed micro-interaction, an intentional page transition. These are proof that a human cared. If you don’t polish, you don’t earn trust. ### 3. The Pivot Tax AI excels at the Happy Path: the most common patterns, the most predictable flows. But "good enough" AI architecture is almost always brittle. This produces what we call **Logic Drift**: subtle regressions and incomplete error handling that surface only under stress. The result is a Pivot Tax. The moment a business needs to scale, integrate a payment processor, or handle a gnarly edge case, the prompted foundation collapses. What felt "good enough" in March becomes a full architectural rewrite by September. ## The Three Pillars of the Precision Standard The Precision Standard isn’t about more hours. It’s about increasing the **density of your intent** — moving from prompt operator to systems thinker. ### 1. UX Polish: The Absence of Friction Precision UX isn’t about "making it pretty." It’s about the absence of friction. AI can generate a standard layout, but it can’t feel the wrongness of a 200ms delay in a search bar, or the frustration of a modal that won’t dismiss the way a user expects. The Precision Standard focuses on the details that "don't matter" until they do: * **Anticipatory Design:** Predicting what the user wants to do next and pre-fetching the data. * **Edge-Case Elegance:** How does the app look when the internet is slow? When the search returns zero results? * **Sensory Feedback:** Haptics, transitions, and layout stability that make software feel as tangible as a well-made instrument, not a digital chore. ### 2. Architectural Integrity: The Unhappy Path AI builds for the prompt. The Precision professional builds for the system: the Unhappy Path, the 20% of cases where things go wrong. While a prompted script might give you a working login flow, a Precision architect is thinking about: * **State Management:** How does this component behave when five different data streams hit it at once? * **Security by Design:** AI routinely suggests outdated libraries and insecure patterns. Precision means understanding *why* a security model works, not just *that* it works. * **Observability:** Building a system that tells you when it’s breaking before the user does. ### 3. Total Intentionality In a flooded market, the first 90% is free. The value lives entirely in the final 10%. The Precision Standard treats "shippable" as the starting line. It’s the final round of QA, the optimization that shaves 50ms off load time, the refusal to ship code that becomes someone else’s debt. ## How to Audit Your Work Three questions to audit whether you're meeting the Precision Standard: 1. **Could a non-technical person generate this output with a 50-word prompt?** If the answer is yes, you haven't added value yet. You’ve just performed a data transformation. 2. **Does this product feel opinionated?** AI is a consensus engine; it produces the average of its training data. Precision work has a point of view. It makes deliberate choices about how a user *should* work. 3. **Is this Write-Only code?** AI produces code that works now but is a nightmare to maintain. Precision work is written for the next developer, not just the current sprint. ## The New Floor What used to pass for "Senior" output is now baseline for an AI agent. A friend of mine has started trolling people by calling their job a Claude Code skill. This isn’t a threat; it’s a filter. The boring, repetitive work that machines do better? Let them have it. What’s left is the work that actually matters — the rigor, the obsession, the systemic thinking that no model can replicate. The "good enough" market is underwater. Stop swimming in it. --- ## https://www.buildfm.com/resource-center/markdown-is-eating-the-world # Markdown is Eating the World ## The Format of Business is Changing Something happened while we were [building our own operating system](/resource-center/system-of-intelligence). We noticed that the connective tissue between every agent, every workflow, every piece of automated intelligence was the same thing: markdown. Not JSON. Not HTML. Not a proprietary file format. Plain, readable, structured markdown. Our proposals start as markdown. Meeting notes get synthesized into markdown. SOWs, internal docs, client briefs — all markdown. This article that you are reading? If you were to look at the files on our server, you would find one for this article that is written in, you guessed it, markdown. Not because we mandated it, but because it's what works when both humans and machines need to read, write, and act on the same content. That realization changed how we think about everything we publish, including this website. ## Why Markdown Matters Now [Markdown](https://daringfireball.net/projects/markdown/) has been around since 2004. It wasn't designed for AI. But it turns out the properties that make it good for humans — lightweight, readable without rendering, structurally expressive — are exactly the properties that make it efficient for machines. **It's human-readable.** You don't need a browser, an app, or a special viewer. Open a markdown file in any text editor and you can read it immediately. In fact, let us show you. Here's the entire syntax you need to know: ``` # This is a heading ## This is a smaller heading This is a paragraph. You just write. **This is bold** and *this is italic*. - This is a list item - This is another one [This is a link](https://www.buildfm.com) > This is a quote. ``` That's it. Congratulations — you just learned markdown. No classes to take, no software to install, no spec to memorize. Everything above is readable *before* it's rendered, and it maps cleanly to the structure of any document you'd ever write. This is why it's winning. **It's machine-readable.** LLMs process markdown natively. When an AI agent needs to understand a document, markdown preserves the semantic structure — headings, emphasis, links, lists — without the overhead of HTML tags, CSS classes, or JavaScript event handlers. **It's token-efficient.** This is where it gets interesting from a cost and environmental perspective. Consider a typical webpage. The HTML source might be 50KB, but the actual *content* — the words, the meaning — might only be 5KB. The rest is markup, styling, scripts, and structural noise. When an LLM processes that HTML, it's spending tokens on `
` instead of the sentence inside it. Markdown strips that ratio down dramatically. You get the structure and meaning with a fraction of the tokens. ## The Environmental Math This isn't just an efficiency argument. It's an environmental one. Every token an LLM processes requires compute. Compute requires energy. When millions of AI agents crawl the web to gather information, they're processing vast amounts of HTML, JavaScript, and CSS that contains no useful information. It's the digital equivalent of shipping products in boxes ten times their size. If a webpage's meaningful content is 10% of its HTML source, then 90% of the tokens spent processing it are waste. Multiply that across every AI-powered search, every agent gathering context, every RAG pipeline pulling from the web — the energy cost of that inefficiency is staggering. Markdown doesn't solve climate change. But when the format of information exchange can reduce token consumption by an order of magnitude, it's worth paying attention to. ## What We Built We put this philosophy into practice on our own site. If you look at the top of this page, you'll see a slim bar with two options: **Human** and **Machine**. You are reading the human version of this article right now. Click **Machine**, and the page transforms. Instead of the rendered website, you see the raw markdown representation of everything on the page — headings, paragraphs, links, team bios, all of it. Clean, structured, portable. You can copy it, paste it into any tool, feed it to any LLM, or just read it. This isn't a gimmick. It's a statement about how we think content should work: every page should be legible to both audiences. **How it works on the client side:** When you toggle to Machine mode, the site dynamically converts the rendered page content into markdown using [Turndown.js](https://github.com/mixmark-io/turndown). It clones the DOM, strips away navigation, scripts, and decorative elements, and produces a clean markdown document. The conversion is lazy — it only runs when you first toggle — and cached per route. The entire library adds roughly 10KB to the bundle, loaded on demand. ## The Part We're Most Excited About Here's where it gets really interesting. We didn't stop at a client-side toggle. We built content negotiation directly into our server. Any HTTP client — including an LLM, an agent, or a simple `curl` command — can request any page on our site as markdown: ``` curl -H 'Accept: text/markdown' https://www.buildfm.com/resource-center/markdown-is-eating-the-world ``` That's it. No special API. No separate endpoint. No API key. The same URL that serves a human-readable webpage will return clean, token-efficient markdown to any machine that asks for it. Standard HTTP content negotiation — the way the web was designed to work. Every page on our site speaks both languages. A browser gets HTML. An agent gets markdown. Same URL, same content, different format for different audiences. To close the loop, we added instructions to our [`llms.txt`](/llms.txt) file — the emerging convention for communicating with AI crawlers — telling any LLM that visits our site to use the `Accept: text/markdown` header. The file already describes who we are and what we do. Now it also tells machines *how* to read us efficiently. Any agent that checks `llms.txt` before crawling will know it can get clean markdown from every page, skipping the expensive HTML-to-text conversion entirely. We think this is what the web should look like when machines are first-class consumers of information. Not a separate "API" bolted onto the side. Not a scraping-friendly sitemap. Just proper content negotiation — the same pattern the web has supported since HTTP/1.1, finally being used for something it was always capable of — combined with a simple, discoverable instruction file that tells machines the best way to consume your content. ## What This Means We're not suggesting everyone rebuild their website to serve markdown. But we are suggesting that the format of business communication is shifting, and the organizations that recognize it early will have an advantage. When your content is markdown-native: - **Your AI agents work better.** They spend tokens on meaning, not markup. - **Your workflows compose.** Markdown flows cleanly between tools, systems, and people without conversion. - **Your content is portable.** No vendor lock-in, no proprietary formats, no rendering dependencies. - **Your environmental footprint shrinks.** Less compute per interaction, across every automated process. Marc Andreessen famously said software is eating the world. Two decades later, we'd argue the format is narrowing. Markdown is becoming the lingua franca of the human-machine interface — not because anyone decided it should be, but because it's the simplest format that both audiences can read. --- *At FM, we build software that works for humans and machines alike. If you're thinking about how AI fits into your content, your operations, or your product — [let's talk](/get-started).* --- ## https://www.buildfm.com/resource-center/the-high-cost-of-free-code # The High Cost of Free Code: Why Builders Must Become Architects ## The Feature Paradox Tareq Ismail recently posed a [thought experiment](https://x.com/tareqismail/status/2016170459163984175?s=12&t=dauP6nPpLvjza3arcN898w) that should keep every builder awake: If you could ship a thousand perfectly engineered features tomorrow with a single prompt, would your product be better? The intuitive answer is "yes." More power, more utility, more value. The reality is the opposite. You would likely end up with something simultaneously more powerful and entirely useless. You would have built a digital Winchester Mystery House—a sprawling, incoherent mess of rooms that lead nowhere and doors that open into walls. In the old world, the cost of engineering acted as a natural filter for bad ideas. If a feature took six weeks and $50k to build, you made damn sure it was worth building. The scarcity of developer hours was a crude but effective form of product management. In a world where AI makes the marginal cost of code near zero, that filter is gone. We are entering the era of **The High Cost of Free Code.** ## The Jevons Paradox of Software Economist William Stanley Jevons observed in 1865 that as technological progress increases the efficiency with which a resource is used, the total consumption of that resource actually rises. We're seeing this play out in real-time. AI hasn't made us build *less* code; it has made us flood the world with it. When code is "free" to generate, the temptation is to solve every edge case with a new button, a new toggle, or a new dashboard. But while the *creation* of that code is cheap, the *cognitive load* it places on the system—and the human using it—is more expensive than ever. Every new feature is a new surface area for bugs, a new path for a user to get lost, and a new piece of "state" that your system has to maintain. The code might be free to generate, but the complexity is a permanent debt. In this environment, **the most dangerous person in your company is the person who says "yes" to every feature request because 'it only takes five minutes to build.'** ## Masons Need Not Apply For decades, the "Virtuoso" in software was the mason—the person who could lay bricks of code faster and more precisely than anyone else. The industry worshipped the "10x Developer" who could out-code a room full of seniors. But when the bricks can lay themselves, the value of the mason evaporates. The new high-leverage skill isn't laying bricks; it's **Urban Planning.** The most valuable builders of the next five years won't be the ones who can prompt the most features into existence. They will be the **Product-First Engineers.** These are individuals who have a deep, visceral understanding of the user's problem and the business's P&L, paired with the technical ability to execute. When you give an engineer with a strong product mindset an AI co-pilot, they become disproportionately effective. Why? Because they know when to *stop*. They are the ones who look at a request for a new feature and say: *"We could build this in ten minutes, but it will confuse 10% of our users for the next two years. Let's solve this with a process change instead."* This hybrid skill set—ruthless product intuition combined with technical fluency—is the only skill that doesn't depreciate. If your only value is "building the thing," you are a commodity. If your value is "knowing what thing to build," you are the architect. ## Disciplined Product Management is the New Strategy In a world of infinite features, **Disciplined Product Management** moves from a "nice-to-have" organizational function to the core of the business strategy. PMs used to be project managers—tracking tickets, managing timelines, and ensuring the "builders" were building. In the AI era, the PM's job shifts from **Production Management** to **Complexity Management.** Their primary tool is no longer the roadmap; it's the **Pruning Shears.** A disciplined PM understands that every "Yes" is a slow-acting poison to the user experience. They understand that a product's value isn't measured by what it *can* do, but by how effectively it helps the user achieve a specific outcome. As the cost of building drops, the value of **Intent** skyrockets. The longest feature list has never been a proxy for the best product — and now that anyone can generate one, it's not even a differentiator. What remains is clarity: a ruthless understanding of the "happy path" and the discipline to protect it. ## The Shift in Leverage As builders, we have to rethink where our leverage comes from. * **From Code Scarcity to Intent Scarcity.** The bottleneck is no longer "how do we build this?" but "why does this exist?" * **From Durable Features to Ephemeral Solutions.** If software is cheap to generate, why should it be permanent? The best "feature" might be a piece of code that is generated on-the-fly to solve a specific user's problem and then deleted, leaving no residue of complexity behind. * **From Masonry to Urban Planning.** Stop focusing on the individual bricks (the code). Start focusing on the flow of traffic (the user journey) and the utility of the zones (the business outcome). The goal of software was never to "be built." The goal was to solve a problem. In an age of infinite building capacity, the discipline to keep the system small and the intent clear is worth more than any feature you could ship. When anyone can build anything, the only thing that matters is knowing exactly what **not** to build. --- ## https://www.buildfm.com/resource-center/system-of-intelligence # We Built Our Own Operating System. Here's Why. ## The Glass vs. The Water Think of your SaaS stack like a collection of expensive glassware. You've spent years buying the finest crystal: your CRM, your project management tool, your communication platforms. But the value isn't in the glass. The value is in the water, the data inside. For years, SaaS companies have thrived by making their "glass" opaque. They want you to believe you need their specific UI, their reporting logic, their "AI-powered" features just to access your own data. They want you to believe that "Pipedrive is how we sell" or "Linear is how we build." The result is what I call the SaaS Tax: you pay more every year for features you don't use while your data remains trapped in silos. Worse, you hire people to act as human bridges, coordinators whose job is to manually move information from the CRM glass to the project management glass to the communication glass. We decided to stop paying that tax. ## What We Actually Built At FM, we still use Pipedrive for CRM and Linear for project management. We're not religious about tools. But we stopped treating them as the center of our operations. Instead, we built an agentic layer that sits above everything. Here's what that looks like in practice: **Proposal Generation** pulls meeting notes and Pipedrive deal context to create branded PowerPoint proposals. No one manually assembles slides anymore. **Meeting Synthesis** takes raw meeting notes, structures them into documentation, and commits them to our knowledge base automatically. The insight doesn't die in someone's notebook. **Weekly Synthesis** generates client updates by pulling from meetings, Slack conversations, and Linear tickets. It creates internal docs and drafts client emails. What used to take our team hours of Monday morning work now happens automatically. **SOW Builder** generates Statements of Work with consistent language, type-specific templates, and dual storage to Google Docs and GitHub. Same quality every time, fraction of the effort. **Company Research** takes a prospect name, runs web research, pulls CRM context, and generates a tailored sales call script. Our team walks into calls prepared without the prep work. **Content Brainstorm** helps us generate newsletter content with FM's voice, incorporating web research and exporting directly to our editor. Each agent crosses system boundaries that used to require human coordination. The Proposal Generation agent doesn't care that deal data lives in Pipedrive and meeting notes live somewhere else. It just assembles what's needed. ## The Shift in How We Think About Software This changed how we evaluate tools. We now buy based on one criterion: the API. If a tool doesn't have a solid API, we won't use it. The UI is almost irrelevant because our team increasingly interacts with data through our own interface, not the vendor's. It also changed how we think about "AI features" inside SaaS products. Most vendors are currently bolting on AI and charging $30/user/month for features that summarize your notes or suggest next steps. That intelligence is locked inside their glass. We'd rather build intelligence that sees across all our systems at once. That's where the leverage actually lives. ## When This Makes Sense I want to be honest about the threshold here. Building your own operating layer isn't always worth it. **It makes sense when:** You have at least 3-4 core systems that need to talk to each other. You're paying for coordination labor (even if you don't call it that). Your workflows have enough repetition that automation compounds. And you have access to someone who can build and maintain custom integrations. **It doesn't make sense when:** You're a team of five people who can just talk to each other. Your tools already integrate well enough through native connections. The coordination cost is low. Or the build cost exceeds several years of the "tax" you're currently paying. For FM, the math was clear. We were spending real hours every week on work that was essentially moving water between glasses. The agents we built paid for themselves within months. ## The Bottom Line The "System of Record" mentality made sense when software was expensive and scarce. You picked your platform, committed to it, and built your processes around its constraints. That era is ending. When building custom integrations costs a fraction of what it used to, the smart move is to treat your SaaS tools as replaceable databases with APIs and build your own logic on top. You don't need to replace your tools. You need to stop letting them dictate how you work. --- *At FM, we help companies build operational intelligence through AI and systems thinking. If you're ready to move your AI agents from prototype to production-grade operations, [let's talk](/get-started).* --- ## https://www.buildfm.com/resource-center/vibe-check-is-not-a-strategy # The 'Vibe Check' is Not a Strategy ## Why Evals are the New Product Requirement Most AI agent projects follow a predictable, doomed path. The Product Owner (PO) watches a demo. The agent successfully researches a company, finds a key contact, and drafts a personalized email. It looks like magic. The PO says, “Great, let’s ship it.” Then, in production, the agent hallucinates a CEO’s name, tries to email a dead domain, and gets stuck in an infinite loop searching for a LinkedIn profile that doesn’t exist. The project stalls. Stakeholders lose faith. The "magic" evaporates. The problem wasn't the model. The problem was that the product was built on a **"vibe check"** rather than engineering rigor. As a Product Owner in the agentic age, your role has fundamentally shifted. You are no longer just managing a backlog of features; you are managing a **Success Rubric**. ## The End of Deterministic Thinking In traditional software, if a user clicks "Submit," a specific row is created in a database. It is deterministic. You test it once; if the code doesn't change, the result doesn't change. AI agents are probabilistic. A single prompt adjustment designed to fix a minor formatting issue might inadvertently break the agent’s ability to handle a complex edge case three steps later. In the world of Large Language Models (LLMs), this is a "regression," and it is a silent killer of product momentum. If your current testing process involves you or a QA lead manually running five prompts to see if the output "looks right," you aren't building a product—you're managing a science experiment. ## Your New Primary Artifact: The Grader For a PO, the most important artifact is no longer just the PRD. It’s the **Eval Harness**. Evaluations (evals) are automated tests that run your agent through hundreds of scenarios to see where it breaks. But for these to work, someone has to define what "good" actually looks like. That is the PO’s new core responsibility. Borrowing from the framework recently [highlighted by Anthropic](https://www.anthropic.com/engineering/demystifying-evals-for-ai-agents), we need to move from manual spot-checks to **automated graders**. As a PO, you must define the rubrics that these graders use to judge the agent: * **The Accuracy Rubric:** Did the agent actually solve the user's problem? (e.g., "Did the refund amount match the invoice?") * **The Constraint Rubric:** Did it stay within legal and brand guardrails? (e.g., "Did the agent refrain from offering a discount it wasn't authorized to give?") * **The Efficiency Rubric:** Did it take 10 steps to do something that should take two? When you define a feature, you must simultaneously define the **Grader** for that feature. If you cannot define how to measure success programmatically, you haven’t defined the feature well enough to automate it. ## Why Evals are a Competitive Advantage Building an eval harness often feels like "extra work" that slows down the initial demo. This is a fallacy. Evals are actually the only way to move fast. **Speed of Iteration** When you have 100+ evals that run in minutes, your developers can experiment with new prompts or models without fear. They know within seconds if they broke a "gold standard" case. **Operational Intelligence** Evals give you a data-driven way to tell stakeholders exactly how reliable the system is. *"The agent is 94% successful on refund requests"* is a business statement. *"It seems to work pretty well"* is a liability. **Model Agnosticism** When a cheaper or faster model is released—like the jump from Claude 3 Opus to 3.5 Sonnet—your evals tell you instantly if you can switch without losing quality. You are no longer locked into a specific provider's "vibes." ## Start with the Failure At FM, we tell our partners: **Don't start with the happy path.** If you're building an agentic system, your first sprint shouldn't be the "perfect demo." It should be identifying the 20 ways the agent is most likely to fail and writing an eval for each one. The companies that win the AI race will be the ones with the most rigorous feedback loops. They will be the ones who turned "vibes" into versioned, tested, and scalable operations. **Is your product built on a vibe or a rubric?** --- *At FM, we help companies build operational intelligence through AI and systems thinking. If you're ready to move your AI agents from prototype to production-grade operations, [let's talk](/get-started).* --- ## https://www.buildfm.com/resource-center/build-vs-buy-agent-age # Build vs. Buy in the Age of AI Agents ## What Cursor vs. Sanity Tells Us About Custom Software Two articles crossed my desk this week that crystallize a tension every business leader should be thinking about. Lee Robinson, who works at Cursor, [wrote](https://leerob.com/agents) about migrating cursor.com from a headless CMS to raw markdown files and code. He spent $260 in AI tokens and three days to do what he estimated would have taken weeks. The site is faster, cheaper to run, and his team can now just ask an AI agent to make changes instead of clicking through CMS interfaces. Then Sanity, the CMS company Cursor migrated away from, published a thoughtful [rebuttal](https://www.sanity.io/blog/you-should-never-build-a-cms). Their argument: yes, you can rip out a CMS in a weekend, but what happens next? All the problems that CMS solved will slowly creep back in. Content approval workflows. Preview environments. Multi-language support. Version tracking. You will end up building your own CMS whether you intended to or not. Both sides make excellent points. And both are right in ways that matter for how you should think about software investment. ## The Cursor Argument: Abstraction Layers Are Now Expensive Lee's core insight is worth repeating: with AI and coding agents, the cost of an abstraction has never been higher. When your team could simply type "@cursor add a new section to the homepage" and have it done in seconds, but instead has to log into a CMS, navigate menus, find the right content type, and manually configure settings, something has gone wrong. The abstraction layer that was supposed to make things easier is now making them harder. This is a real phenomenon. CMS platforms were built for a world where business users needed friendly interfaces because they could not interact with code directly. The GUI was the point. But now that AI can serve as an intermediary between human intent and code, that GUI becomes a bottleneck rather than an enabler. The numbers from Cursor's migration are striking. They removed 322,000 lines of code and replaced them with 43,000. Build times got 2x faster. They stopped paying $56,000 in CDN costs. And most importantly, their team can now ship changes to the website and product in the same pull request. ## The Sanity Argument: You Cannot Delete the Problem Here is where the counterargument gets interesting. Sanity's response acknowledges that Lee's frustrations are valid. Preview workflows are clunky. Authentication fragmentation is annoying. The complexity overhead of headless CMS integrations is real. But they point out something important: look at what Lee actually built to replace the CMS. He built an asset management GUI with "3-4 prompts." He set up user management through GitHub permissions. He has version control through git. Content modeling through markdown frontmatter. Localization tooling. These are CMS features, just distributed across different systems. The features exist because the problems are real. You can delete the CMS, but you cannot delete the need to manage assets, control who can publish what, track changes, and structure content for reuse. Give it six months, Sanity argues. Someone will need to schedule a post. Someone will need to preview on mobile. Someone will need approval workflows. The "simple" system will accrete complexity because content management is complex. ## Where This Leaves Us: The Build vs. Buy Question Just Got Harder I have been preaching the gospel of custom software for years. The core argument: AI-empowered development has made building custom software faster and cheaper than ever. You can create solutions tailored exactly to your business needs rather than paying for SaaS platforms that cover 80% of use cases and leave you working around the other 20%. The Cursor migration is evidence for this view. Lee rebuilt their entire website architecture in three days for $260 in tokens. That is remarkable velocity. But the Sanity response gives me pause. Not because I think they are wrong about CMSs specifically, but because they articulate a principle that applies broadly: when you build your own version of something, you inherit responsibility for every problem that thing was designed to solve. ## The Real Question: What Are You Actually Building? Here is where I land on this. The Cursor vs. Sanity debate is not really about CMSs. It is about where to draw the line between commodity infrastructure and differentiated capability. Some software you should rent. Systems of record, commodity functions, solved problems. Your content repository probably needs to exist somewhere stable and queryable. Your authentication system should probably be Auth0 or Clerk rather than something you built yourself. Your payment processing should be Stripe. These are solved problems where the abstraction layer still provides more value than it costs. Other software you should build. The unique processes that give you competitive advantage. The integrations between systems that are specific to how your business operates. The custom tools that multiply force because they are designed exactly for your workflows. The mistake is treating this as binary. It is not "build everything" or "buy everything." It is about identifying where custom software creates leverage and where commodity solutions are good enough. ## What Changes in the Agent Age AI agents change the equation in a specific way: they reduce the cost of building, but they do not reduce the cost of maintaining. Lee could rebuild Cursor's website architecture in three days because AI agents could write scripts, migrate content, and generate code at remarkable speed. But maintaining that architecture over years requires ongoing attention to all the edge cases that will emerge. The Sanity argument is essentially: yes, agents let you build faster, but faster building does not mean you want to take on every maintenance burden. Do you want to be in the business of maintaining content approval workflows? Or do you want to focus your engineering capacity on things that actually differentiate your product? This is where the "build your own CMS" cautionary tale becomes instructive. CMSs are not exciting. They are infrastructure. The features they provide (versioning, workflows, permissions, preview environments) are necessary but not differentiating. Nobody chooses your product because you have a great internal content management system. ## The Force Multiplication Framework Here is how I am thinking about this for the businesses we work with. Your systems of record should probably stay as off-the-shelf or commoditized solutions. Your CRM, your content repository, your financial systems, your HR platform. These are solved problems. Keep them simple. Maybe move toward open source versions where it makes sense. Maybe simplify how you interact with them. Definitely make sure they are accessible through APIs. But they need to exist because the data repository is valuable. Your force multipliers are where custom software creates disproportionate value. These are the places where connecting systems together, or applying your unique data, or building specific workflows creates outcomes that generic software cannot provide. ### Example A company has broad industry data that nobody else has access to. What if they built a custom intelligence engine that uses that data to power recommendations? That is differentiated capability. That is worth building. ### Example A firm has developed proprietary client assessment methodology. Building custom software that embeds that methodology creates competitive advantage that no off-the-shelf CRM can provide. ### Example A business has unique approval workflows that span multiple departments in ways that no SaaS tool handles well. Custom integration software that connects existing systems together in exactly the right way creates efficiency that compounds. ### The pattern Keep your systems of record, but build the connections and intelligence layers that multiply their value in ways specific to your business. ## The Practical Takeaway When you are evaluating whether to build or buy, ask these questions: **Is this a solved problem?** If thousands of companies have the same need and good solutions exist, lean toward buying. Do not rebuild authentication, payment processing, or basic content storage. **Does custom software here create competitive differentiation?** If the software would embed your unique IP, connect systems in ways specific to your workflow, or enable capabilities that give you advantages competitors cannot replicate, lean toward building. **What is the maintenance burden, and do you want it?** Faster building does not mean zero maintenance. Consider whether the ongoing responsibility of maintaining custom software is worth the benefit. **Can AI agents help you interact with existing systems differently?** Sometimes the answer is not "replace the CMS" but "build an AI layer that lets your team interact with the CMS differently." The system of record stays, but the interface changes. ## The Window Is Open Here is what excites me about this moment: the tools for building custom software have never been better, and the opportunity to create differentiated capability has never been clearer. The companies winning in competitive markets are the ones that recognize software as a strategic asset, not just a cost center. They keep their systems of record stable and boring. They build custom solutions where software creates leverage specific to their business. The Cursor vs. Sanity debate is a healthy one because it forces us to think carefully about where to draw lines. Both "build everything custom" and "buy all SaaS" are wrong answers. The right answer is thoughtful deployment of each approach where it creates the most value. AI agents have lowered the cost of building. That does not mean you should build everything. It means you can now afford to build the things that actually matter. --- *At FM, we help businesses identify where custom software creates leverage and where commodity solutions are good enough. If you are wondering whether to build or buy for a specific business challenge, [let's talk](/get-started).* --- ## https://www.buildfm.com/resource-center/human-architect-ai-builder # The Human Architect & The AI Builder ## Accelerating Agency Delivery with Fantasy **How FM and Fantasy used an intentional "Human-in-the-Loop" collaboration model to deliver a massive multi-brand consolidation project in just six weeks.** In the current hype cycle of artificial intelligence, the narrative often centers on "autonomous agents" replacing developers. But when our partners at [Fantasy](https://fantasy.co) approached us with a complex challenge for a global consumer care leader, we proved a different thesis: AI is most powerful not when it works alone, but when it is strictly guided and inspired by human expertise. The brief was ambitious: unify disparate data streams and multiple sub-brands into a single, cohesive consumer destination. With a rigid six-week timeline from inception to MVP, traditional workflows were unlikely to succeed. To meet this deadline without sacrificing the "best-in-class" experience Fantasy is known for, FM deployed a revolutionary workflow. We moved beyond the idea of "auto-pilot" to a collaborative Human + AI model, where AI provides velocity, and human experts provide direction, consistency, and architectural integrity. ### The Challenge: Unification at Speed The client needed to merge the digital presence of multiple distinct brands into a single, centralized web portal. The technical hurdles were significant: - Complex Data Integration: Combining data streams from three different brands using three different data schemas into a centralized model to power a location-based provider finder. - Legacy vs. Modern: Migrating to a modern stack (Next.js, Payload CMS) on a tight deadline. - High Fidelity: The need to maintain rigorous design standards and performance metrics despite the tight timeline. ### The Philosophy: AI Output, Human Outcome Our approach wasn't about letting AI run wild. It was about Intentional Task Parallelization. We structured the work so that AI agents handled the "first pass" of component generation and data migration, while a lean human team focused on strategy and refinement. As noted in our findings, "AI can deliver useful code and structure quickly, but it needs steady guidance to stay consistent". 1. The Human-Driven "Context" Layer AI models often fail because they lack context. We solved this with Context7, a Model Context Protocol (MCP). While the AI did the searching, humans defined the boundaries. - **Bridging the Knowledge Gap:** Because standard models lacked familiarity with the newest Payload CMS 3.0 patterns, we used Context7 to feed the agents current documentation. - **Prompt Engineering as Development:** High-level human involvement was required for prompt definition and architecture review. We found that reuse of well-structured prompts in GitHub Actions and Claude Code led to consistently better results than ad-hoc requests. 2. The "Glass Box" Reality: Why Autonomy Failed We learned quickly that AI agents were not fully autonomous. Without human intervention, the AI’s "literal" interpretation of designs caused issues: - **Literal Translations:** The AI often interpreted hidden Figma layers or unnecessary rotations as essential code, creating bloated markup. A human developer had to intervene to clean and consolidate these styles. - **Style Consistency:** The AI struggled to create a cohesive typeface system, often duplicating CSS classes instead of reusing them. Human experts were essential to manually consolidate these styles and ensure the "pixel-perfect" finish Fantasy demands. Scaling output without scaling understanding leads to re-work, bugs and frustration: - Left to its own devices, an agent will make hidden assumptions and decisions when writing code. By evolving a workflow that surfaced decisions and assumptions up front, persisted them in our issue tracker, then used any human edits to move to the next step, we were able to significantly reduce technical design and coding errors that are the main cause of expensive and inefficient re-work. ## The Workflow: Hybrid Cloud & Local Control To balance speed with control, we split the workflow based on the level of judgment required: ### The Cloud Stream (High Volume, Low Risk): We used Claude Code GitHub Actions for repetitive tasks. This allowed us to run background development work, but even here, humans remained in the loop—developers could review and trigger these tasks directly from mobile devices via the GitHub app, ensuring oversight even on the go. ### The Local Stream (High Judgment): For complex architectural decisions, we avoided automation. Developers used the Claude Code CLI locally. Initially we used interactive prompting and debugging where human intuition was required to guide the AI through nuanced logic. Eventually we progressed to repeated prompts and consistent workflows to create more predictability and reduce cognitive overhead and agent mistakes. ### The "No-Fly" Zones: We intentionally excluded certain areas from AI workflows. Content edits and Product QA remained manual because human review was simply faster and more reliable than current AI QA tools for early-stage products that were fast changing. ### The Infrastructure: Safety Rails for AI To allow for this rapid iteration, we needed a safety net. We utilized Vercel and Neon to create isolated preview environments for every single pull request. - **Isolated Database Branches:** Neon automatically assigned a unique database branch to each preview. - **Risk-Free Iteration:** This allowed the AI to attempt migrations or configuration updates in a sandbox. If the AI "broke" the database, it only broke its own branch—never the production or even other agents’ data. ## The Results By keeping humans firmly in the driver's seat while using AI as a high-powered engine, we achieved remarkable efficiency. - **Velocity:** MVP delivered above spec in 6 weeks with only 1 designer and 1 developer.. - **Quality:** The site launched, matching or improving upon original designs, with a 97 Performance score and 100 Best Practices score on Lighthouse. - **Efficiency:** We successfully implemented an observable data sync process combining multiple streams into a centralized model. ## Key Takeaway This project proved that the "Human in the Loop" is not a bottleneck—it is the safety valve that makes AI viable for enterprise production. By combining rapid AI output with steady human guidance, FM helped Fantasy deliver a complex platform at a speed and quality impossible with traditional methods. --- ### Ready to accelerate your delivery? *Would you like to schedule a deep-dive to see how our Human + AI collaboration model can shorten your next project's timeline? [Schedule a call](/get-started) to learn more.* --- ## https://www.buildfm.com/resource-center/scaling-without-headcount # Scaling Operations Without Proportionally Increasing Headcount Your CFO drops a question in the leadership meeting: "Revenue is up 35% year-over-year. Great. But operational headcount is up 32%. We're barely improving margins. How do we grow without proportional cost increases?" Good question. The answer: by systematically identifying and automating operational bottlenecks so that additional volume doesn't require additional people. ## The Linear Growth Trap Most businesses default to linear scaling: **Revenue up 30%** → Handle 30% more customers → Process 30% more transactions → Need ~30% more people The math seems inevitable. More work requires more workers. Except it doesn't—if you're strategic about where automation creates leverage. The businesses scaling most efficiently have broken the linear relationship between volume and headcount. They're achieving super-linear growth: 40% revenue growth with 12-15% headcount growth. How? They've identified the specific operational tasks that consume capacity and systematically automated them. ## Map Your Operations to Find the Leverage Points You can't optimize what you don't understand. Start by mapping where your operations team spends time. For two weeks, have key team members track time in broad categories: customer communication, data entry and processing, report generation and analysis, coordination and status updates, problem-solving and decision-making, and administrative overhead. You'll probably find that 60-70% of time goes to a small number of high-volume, repetitive activities. Example from a professional services firm: **Operations team time breakdown:** - 35% - Scheduling and coordination - 20% - Client status updates - 15% - Data entry into project management system - 12% - Report generation - 10% - Problem-solving complex issues - 8% - Administrative overhead The first four categories (82% of time) are prime automation candidates. That 82% represents the opportunity: automate it effectively, and the same team can handle 4-5× the volume. ## Target High-Volume, Repetitive Tasks First ### Customer Inquiry Handling Most customer inquiries fall into predictable patterns. 70-80% of questions are variations on the same 15-20 topics. **Before automation:** 4-person support team handling 400 inquiries weekly **With intelligent automation:** Automation handles ~300 straightforward inquiries, 4-person team handles 100 complex inquiries plus oversight Capacity freed for growth: 3× volume increase possible with same team ### Data Entry and Processing Manual data entry scales linearly—more volume requires more people. Automated data capture and processing scales almost infinitely. Example: Invoice processing **Before:** Team of 3 processing 150 invoices weekly at 25 minutes per invoice **After automation:** Intelligent document processing extracts data, team reviews exceptions - Same 3 people process 500 invoices weekly - 3.3× volume increase with same headcount ### Report Generation Manual reporting consumes shocking amounts of time. **Before:** Operations manager spends 4 hours every Monday compiling weekly ops report (208 hours annually) **After automation:** Automated report pulls data, generates visualizations, distributes (~1 hour annually setting up automation, 207 hours reclaimed) ### Scheduling and Coordination Example: Field service scheduling **Before:** Dispatcher manually schedules 40 service calls daily (2 hours daily, 500 hours annually) **After automation:** System optimizes routes based on location, skills, availability, priority. Dispatcher reviews and adjusts automated schedule (30 minutes daily, 375 hours reclaimed) ## Design Systems That Maximize Employee Productivity ### Automated Dashboards vs. Manual Reporting **Old model:** Employees manually compile information from multiple systems **New model:** Dashboards surface real-time insights; employees use information rather than gather it A operations director told me: "We used to spend 12 hours weekly creating reports for management. Now dashboards show everything in real-time. We spend that 12 hours improving operations instead of reporting on them." ### Self-Service Capabilities Enable customers and internal stakeholders to serve themselves for routine needs: - Customer portal for order status - Automated approval workflows - Self-service analytics Each self-service capability removes load from your operations team. ### Integration Elimination of Manual Data Transfer When systems don't integrate, humans become the integration layer. Example before integration: Sales enters deal in CRM, operations manually copies to project management system, finance manually copies to invoicing system. Data often out of sync, errors common. After integration: Data entered once, flows automatically to all systems. No manual transfer, no sync issues. 15-20 hours weekly reclaimed across teams. ## The Capacity Expansion Formula **Current capacity:** Team size × Hours per week × Productivity rate = Output capacity **Example:** 8 people × 40 hours × 70% productive time = 224 productive hours weekly If your operation requires 5 hours of human work per unit output: 224 hours ÷ 5 hours per unit = ~45 units weekly capacity **After targeted automation:** Same team size, but automation handles 60% of work: - Humans now need 2 hours per unit (40% of previous) - 224 hours ÷ 2 hours per unit = 112 units weekly capacity **Capacity increase: 2.5× with same headcount** That means can handle 150% revenue growth before needing additional hiring, or can reduce team by 2-3 people while maintaining current capacity, or can redirect team to higher-value activities. ## The Strategic Hiring Model ### Traditional Scaling (No Automation) - Year 1: $10M revenue, 50 employees - Year 3: $16M revenue (60% growth), 80 employees (60% headcount growth) - Revenue per employee: Flat at $200K ### Automation-Enabled Scaling - Year 1: $10M revenue, 50 employees - Year 3: $16M revenue (60% growth), 60 employees (20% headcount growth) - Revenue per employee: Increased from $200K to $267K (33% improvement) The automation investment in year 1-2 enables growth without proportional hiring in year 2-3. ## Build Automation That Scales With Volume Prioritize automations where cost/complexity doesn't increase with volume. **Good scaling:** Automated customer inquiry handling - Cost to handle 100 inquiries monthly: $X - Cost to handle 1,000 inquiries monthly: $X + 10% **Poor scaling:** Semi-automated process still requiring significant human oversight per transaction - Scales linearly because human time still required Focus on automations that break the linear scaling pattern. ## The Role Humans Still Need to Play Automation creates leverage, but humans remain essential for: - **Complex problem-solving:** Situations requiring judgment, creativity, or dealing with novel scenarios - **Relationship building:** High-value customer interactions, strategic partnerships, team management - **Strategic decisions:** Planning, prioritization, evaluating trade-offs - **Exception handling:** Edge cases that automation can't handle - **Continuous improvement:** Identifying new automation opportunities, optimizing processes The goal is shifting your team's time allocation from 70% repetitive execution / 30% strategic work to 20% repetitive execution / 80% strategic work. ## The Real-World Pattern **Stage 1 (Year 1):** - Revenue: $8M - Operations team: 15 people - Revenue per ops employee: $533K - Identify automation opportunities, implement first automations **Stage 2 (Year 2):** - Revenue: $11M (37% growth) - Operations team: 16 people (7% growth) - Revenue per ops employee: $688K - Early automation paying off, expand automation scope **Stage 3 (Year 3):** - Revenue: $15M (36% growth from year 2) - Operations team: 17 people (6% growth) - Revenue per ops employee: $882K - Automation compound effects **Result over 3 years:** - Revenue: +87% - Headcount: +13% - Revenue per employee: +65% That's super-linear scaling enabled by strategic automation. ## The Investment Timeline Don't expect instant results. Automation impact compounds: **Months 1-3:** Planning, implementing first automations. Cost investment, minimal capacity impact yet. **Months 4-9:** First automations stabilize, expand scope. Beginning to see capacity freed up. **Months 10-18:** Compound effects, multiple automations working together. Significant capacity expansion visible. **Months 18+:** Continuous optimization and expansion. Automation becomes part of how the organization operates. The businesses that fail at automation expect month-1 results. Those that succeed commit to 12-18 month transformation knowing the payoff compounds. ## The Bottom Line Scaling operations without proportional headcount growth requires: 1. **Map where time goes** (you can't optimize what you don't measure) 2. **Target high-volume repetitive tasks** for automation (maximum leverage) 3. **Design systems that maximize employee productivity** (dashboards, self-service, integration) 4. **Build automation that scales with volume** (preferably sub-linearly) 5. **Redirect human capacity to high-value work** (judgment, relationships, strategy) The result isn't static headcount—you'll still hire as you grow. But the ratio shifts from 1:1 (revenue growth: headcount growth) to 3:1 or 4:1. That shift drives margin expansion (revenue grows faster than costs), more sustainable growth (less dependent on hiring in tight labor markets), better work quality (team focused on interesting work), and competitive advantage (you can profitably serve markets competitors can't). The companies dominating their industries over the next decade will be those that master super-linear scaling through strategic automation. Your operations team should be a competitive advantage, not a cost center that scales linearly with revenue. Automation makes that possible. The question is whether you'll do it proactively before competitors do, or reactively after you've lost margin advantage. --- ## https://www.buildfm.com/resource-center/ai-development-timelines # How Long Does It Actually Take to Build Custom Software with AI-Empowered Development? A prospective client called last week with a familiar question: "We need custom software for our operations. How long will it take?" I asked what timeline they were expecting. "Six to nine months, based on what traditional development firms quoted us." I told them we'd have a working prototype in their hands within three weeks and a production-ready MVP in 8-10 weeks. They didn't believe me. Modern AI-empowered development has completely changed the timeline calculus for custom software. Here's what you need to know. ## The Old Timeline Model Is Dead Traditional custom software development followed a predictable pattern: **Weeks 1-8:** Discovery and requirements gathering. Meetings, documentation, use cases, user stories, technical specifications. **Weeks 9-12:** Design phase. Mockups, user flows, technical architecture documents, database schemas. **Weeks 13-28:** Development. Occasional updates but nothing functional to review. **Weeks 29-32:** Testing and bug fixes. Your first chance to actually use the software. **Weeks 33-36:** Revisions based on the gap between specifications and reality. **Week 37+:** Launch, usually discovering the real requirements only after users start using it. Total timeline: 9+ months. That assumes everything goes smoothly, which it rarely does. This model made sense when coding was the bottleneck. Every line of code required significant time, so extensive planning was necessary to avoid expensive rework. Coding isn't the bottleneck anymore. ## The New Reality: Iteration Over Specification AI-empowered development prioritizes working software over comprehensive documentation. Here's what modern development actually looks like: **Week 1-2:** Rapid discovery. Collaborative sessions where we understand your core problem, key workflows, and critical constraints. Output: shared understanding, not 50-page specifications. **Week 3-4:** Working prototype. Actual functional software you can click through, test with real users, and evaluate. It won't have every feature, but it demonstrates core functionality. **Weeks 5-12:** Iterative development. Regular releases (usually weekly or bi-weekly) where you see progress, provide feedback, and influence direction. New features, refined interfaces, and expanded capabilities rolling out continuously. **Weeks 8-12:** Production hardening. Security review, performance optimization, user acceptance testing. **Week 10-12:** Launch. You've been using and refining the software for weeks, so launch becomes a milestone rather than a nail-biting reveal. Total timeline: 10-12 weeks for an MVP. You've been seeing and using working software since week 3. ## Why AI Accelerates Development So Dramatically AI fundamentally changes what developers spend time on. **Boilerplate code generation:** AI writes repetitive, structural code in seconds—authentication systems, database connections, API endpoints, form validation. Developers review and customize rather than writing from scratch. **Real-time error detection:** AI catches common errors while developers code, preventing bugs that would require debugging time later. **Pattern recognition:** AI suggests implementations based on similar applications, accelerating decision-making about common problems. **Automated testing:** AI generates test cases based on code, catching issues faster. **Documentation creation:** AI generates initial documentation from code, which developers refine rather than write from scratch. The result? Developers spend 60-70% of their time on problems that require human expertise—business logic, architecture, user experience, complex integrations. The remaining 30-40% on routine implementation gets accelerated by AI. A feature that took two weeks now takes 3-5 days. Multiply that across every feature in your application, and timelines compress dramatically. ## What Actually Determines Timeline Not all custom software takes 10-12 weeks. Timeline depends on several factors: ### Scope and Complexity **Simple automation tool:** 4-6 weeks Example: Automating a specific workflow with defined inputs/outputs, limited user interface, integration with 1-2 existing systems. **Standard business application:** 8-12 weeks Example: Customer portal, internal operations tool, data management system with moderate complexity. **Complex platform:** 4-6 months Example: Marketplace with multiple user types, extensive integrations, sophisticated business logic, high transaction volume. **Platform modernization/replacement:** 3-8 months Example: Replacing legacy system while maintaining business continuity and migrating data. Even complex projects deliver incremental value throughout rather than one big release at the end. ### Integration Requirements The more systems your software needs to integrate with, the more the timeline extends—not because integration is technically difficult, but because it requires understanding how those systems work and testing thoroughly. Well-documented modern APIs: minimal time added. Legacy systems with poor documentation: can add weeks. ### Unknowns and Uncertainty Clear requirements and stable scope: predictable timeline. Evolving requirements and exploratory development: timeline extends, but the iterative approach means you're learning and adjusting rather than committing to wrong specifications. ### Team Availability If your team can provide rapid feedback and decision-making, development accelerates. If feedback takes weeks because stakeholders are busy, the timeline extends accordingly. We've seen projects slow down because client stakeholders couldn't review progress weekly. Build that time into your planning. ## The Continuous Delivery Advantage Traditional development asks you to bet months of investment on specification documents before seeing results. Modern development asks you to evaluate working software weekly. This dramatically reduces risk: **Week 3:** "This core workflow doesn't quite work how we expected. Let's adjust." Cost to change: minimal, course correction happens immediately. **Traditional approach, month 6:** "This core workflow doesn't work how we expected, but we've already built the entire system around it." Cost to change: massive rework or accepting flawed software. One client realized during their week 4 demo that they'd mis-specified a critical approval workflow. We adjusted course immediately. Total impact: 2 days of rework. With traditional development, they wouldn't have discovered this until month 8, requiring either extensive rework or living with a system that didn't match their actual process. ## The Production Timeline vs. Feature Timeline 10-12 weeks to MVP doesn't mean "done forever." It means functional software serving real users, delivering real value. After launch, development continues: **Months 2-4:** Refinements based on real usage, additional features, optimization. **Months 4-6:** Expanded functionality, integrations, scaling improvements. **Ongoing:** Continuous enhancement as business needs evolve. This is actually cheaper than traditional development because you're only building features users actually need, validated through real usage rather than speculative requirements. ## Why Some Projects Take Longer Not every custom software project hits these timelines. Here's what extends development: **Unclear requirements:** If stakeholders can't agree on priorities or keep changing direction, development slows. Iterative development handles this better than traditional approaches, but clarity still matters. **Complex compliance requirements:** Healthcare, financial services, government contracting—regulatory requirements add time. **Legacy system integration:** Connecting to old systems with poor documentation requires exploration and testing. **High-transaction systems requiring extensive optimization:** Software that needs to handle thousands of concurrent users or complex real-time processing requires performance engineering. **Extensive customization requirements:** When every workflow is unique and requires custom logic, development takes longer than systems with reusable patterns. Even these should show progress in weeks, not months of invisible work. ## The Questions You Should Ask Development Partners When evaluating developers, ask: **"When will we see working software we can actually test?"** If the answer is longer than 3-4 weeks, they're using outdated approaches. **"How often will we see progress and provide feedback?"** If it's less frequent than bi-weekly, they're not doing iterative development. **"What will you deliver in the first 30 days?"** If the answer is specifications and designs without functional software, run. **"How do you handle when our requirements change during development?"** If they treat changing requirements as costly scope creep rather than expected learning, they're stuck in waterfall thinking. ## The Bottom Line Custom software development in 2025 is fundamentally different than even five years ago. AI-powered development tools, modern frameworks, cloud infrastructure, and iterative methodologies have compressed timelines dramatically. If you're being quoted 6-9 month timelines for custom software that could be in production in 8-12 weeks, you're talking to developers using 2015 approaches. Speed to market matters more than comprehensive specifications. Iterative learning beats extensive planning. Working software beats detailed documentation. Time to market is competitive advantage. The companies that can build, test, learn, and iterate in weeks rather than months will outmaneuver competitors still planning in conference rooms. Which timeline are you operating on? --- ## https://www.buildfm.com/resource-center/procivica-case-study # How ProCivica Scaled Nationally with Custom Software: A Case Study **Building a custom learning management platform that enabled national expansion while reducing operational overhead by 50%** ## The Challenge: Trapped by Success ProCivica had built something remarkable. Their online, court-mandated educational courses were creating lasting behavioral change for thousands of learners across 354 communities. With 35,000+ graduates and a 90% student satisfaction rate, they had proven their unique approach—the **ProCivica® Behavioral Civics Method**—worked. But success brought its own challenges. The company had reached a critical inflection point. Their off-the-shelf learning management system, combined with various third-party tools and manual workarounds, had gotten them to where they were. But it couldn't take them where they needed to go. "We were spending more time managing our systems than we were serving our mission," explains Chip Morris, CEO of ProCivica. "Every new court partnership, every new course, every operational improvement we wanted to make required working around the limitations of our existing platforms. We knew we needed something built specifically for how we work—not how a generic LMS thinks education should work." The operational bottlenecks were clear: - Manual processes for managing court partnerships and learner enrollment - Disconnected systems requiring duplicate data entry - Limited ability to customize the learning experience - Difficulty tracking and reporting on learner progress across jurisdictions - Constraints on creating new courses and content - Scaling challenges that would require hiring additional operations staff Most critically, they were **blocked from pursuing national expansion**. The infrastructure they had built their business on simply couldn't support the growth they were ready to achieve. ## The FM Approach: Building for the Future FM partnered with ProCivica through our **Software Within Reach Project**—a guided journey from concept to realization designed specifically for growing businesses ready to take ownership of their technology. ### Discovery and Design We started with a comprehensive analysis of ProCivica's operations. Rather than simply asking what features they wanted in a new system, we observed how their team actually worked. We looked for: - Trapped value in manual processes - Workarounds that had become normalized - Friction points in the user journey - Opportunities for automation - Growth constraints in the existing architecture What emerged was a clear picture: ProCivica needed more than a better LMS. They needed a **bespoke learning management platform** that could serve as the foundation for their entire business—something they owned, could shape, and could extend as their needs evolved. ### The Solution: A Custom-Built Platform Over 7 months, our team built an end-to-end platform designed specifically for ProCivica's unique business model. This wasn't about recreating generic LMS functionality—it was about building exactly what ProCivica needed to scale nationally while reducing operational overhead. **The Technology Stack:** We selected modern, proven technologies that would give ProCivica flexibility, performance, and maintainability: - **React/Next.js/Tailwind** for a fast, responsive user interface - **Payload CMS** for managing content models, users, and digital assets - **Stripe** for secure payment processing - **Resend** for transactional email orchestration - **Vercel and GitHub** for hosting and infrastructure This architecture went far beyond a simple marketing website—it **is the ProCivica business**. Every aspect was designed to support their mission of building stronger citizens and creating stronger communities. **Key Platform Features:** - **Multi-tenant court management** - Seamlessly manage partnerships with courts and judicial agencies across the country - **Learner enrollment and tracking** - Automated processes from registration through course completion and certification - **Custom course builder** - Easy content management for ProCivica's diverse curriculum - **Real-time progress dashboards** - Give probation officers, prosecutors, and judges visibility into participant progress - **Integrated payment processing** - Streamlined purchasing flow for individuals and bulk enrollments - **Certificate generation** - Automated production and delivery of completion certificates - **Responsive design** - Accessible learning experience across phones, tablets, and computers - **Reporting and analytics** - Track outcomes and demonstrate impact to stakeholders ## The Launch: A Smooth Transition Launch day arrived after months of careful planning and preparation. The FM team was up at 5:30 AM to support ProCivica through the cutover. **The migration included:** - 200 academies moved into the new system - Historical learner data and progress tracking - All course content and materials - Court partnerships and administrative users Within 2 hours, the platform was live and users were already arriving. By noon, the first purchase came through Stripe. A few hours later, a learner completed their first online course on the new platform. It was alive. ## The Results: Transformation Through Custom Software The impact of the new platform was immediate and measurable: ### Operational Efficiency - **65% increase in operational efficiency** through automated processes - **50% reduction in operational costs** by eliminating manual workarounds - Staff freed from administrative tasks to focus on mission-critical work - Ability to scale without proportional increases in operational overhead ### Business Growth - **National expansion enabled** without infrastructure constraints - **4-month ROI timeline** based on operational savings and growth opportunities - Foundation for new revenue streams and partnership models - Competitive advantage through technology ownership ### Strategic Value - **Ownable intellectual property** that increases enterprise value - Platform that can evolve with the business, not constrain it - Data and analytics to demonstrate impact to stakeholders - Technology foundation that supports ProCivica's long-term vision ## The Power of Ownership Perhaps the most significant outcome isn't captured in metrics: ProCivica now owns their platform. Not borrowed or rented, but something they can shape and extend into something truly unique. This ownership means: - Freedom to innovate without vendor constraints - Ability to respond quickly to market opportunities - Control over their technology roadmap - Foundation for building defensible competitive advantages "The moment we went live, I felt like we had finally become the company we were meant to be," says Chip Morris. "We're no longer working around our systems—our systems are working for us. That changes everything about how we can serve our mission and grow our impact." ## The Bigger Picture: AI-Accelerated Development What makes this story particularly noteworthy is what **wasn't** possible just 18 months earlier. Through FM's AI-empowered development process, we were able to build something extraordinary with a small team in 7 months that would have previously required a team 4 times as large and significantly more investment. This is the new reality of custom software development. Technologies and approaches that make original software accessible to growing businesses—not just enterprises with million-dollar IT budgets. ## Lessons for Other Growing Businesses ProCivica's transformation offers valuable lessons for any business wrestling with similar challenges: ### 1. Don't Wait Until Systems Completely Break ProCivica recognized their constraints while still growing. They didn't wait for a crisis—they proactively addressed limitations before they became emergencies. ### 2. Ownership Has Strategic Value The ability to control your technology roadmap and build proprietary capabilities creates competitive advantages that off-the-shelf solutions can't provide. ### 3. Custom Doesn't Mean Unaffordable With modern AI-empowered development approaches, custom software is more accessible than many businesses realize—especially when weighed against the ongoing costs and constraints of inadequate platforms. ### 4. Technology Should Enable Mission The best software solutions fade into the background, letting teams focus on what they do best. ProCivica's team now spends time on education innovation, not system management. --- ## Ready to Transform Your Operations? If you're experiencing similar constraints—if your current systems are preventing you from reaching your potential—we'd love to explore how custom software could transform your business. **[Get Started](/get-started)** or **[Learn More About Our Approach](/solutions)** --- ## About ProCivica ProCivica provides online, court-mandated educational courses designed to create lasting behavioral change. Operating across 354 communities with 35,000+ graduates, ProCivica combines cognitive-behavioral therapy tools with civic responsibility training through their proprietary ProCivica® Behavioral Civics Method. Learn more at [procivica.com](https://procivica.com). --- ## https://www.buildfm.com/resource-center/preparing-team-for-ai-adoption # Preparing Your Team for AI Adoption Without Disrupting Operations Most AI adoption strategies focus on the technology and completely ignore the human side. You can't just turn on AI tools and expect transformation. You need a structured approach that builds confidence without overwhelming people or disrupting the work that keeps your business running. We like to think of it as both a top down and bottom up approach. Top down means setting clear expectations and goals for AI adoption. Bottom up means empowering your team to experiment and learn on their own. ## Start With Problems, Not Tools The biggest mistake in AI adoption is starting with the tool. "Everyone needs to learn ChatGPT!" or "We're implementing this AI platform across the company!" That's backwards. Start by identifying specific, frustrating problems your team faces daily. The analyst who spends three hours every Monday compiling report data. The customer service team drowning in routine inquiries. The marketing person manually resizing images for different platforms. These are perfect AI adoption starting points because people already want them solved, success is obvious and measurable, and failure doesn't break anything critical. We worked with an operations team that started their AI journey by using AI to automate their weekly operations report. It saved their ops manager 4 hours every week. That single success created more momentum than any company-wide mandate could have. ## The Champion Model Works Better Than Top-Down Mandates Corporate mandates create compliance, not capability. You want capability. Instead of requiring everyone to use AI immediately, identify people on each team who are naturally curious and willing to experiment. These become your AI champions—not because they have a fancy title, but because they're using these tools and seeing results. Your sales team has someone who's already experimenting with AI for email drafting. Give them time to develop real expertise. Then have them share specific use cases: "Here's how I use AI to personalize cold emails, and it increased my response rate by 35%." That's worth ten times more than any training manual. Champions help teammates with questions, share techniques that work, and build confidence through peer support rather than top-down pressure. ## Hands-On Training Beats Theoretical Education Every Time Most AI training fails because it's too theoretical. People sit through presentations about what AI can do in general, then have no idea how to apply it to their actual work. Effective training is hands-on and specific to your operations. Your customer service team learns by using AI on actual customer inquiries. Your finance team learns by using AI on real budget analysis. We ran a one-day AI workshop with a studio production company. Instead of teaching general AI concepts, we worked through their actual challenges: How do you use AI to run better meetings? How do you synthesize asks into project proposals and presentations? By the end, they weren't AI experts, but they had solved real problems and knew how to continue learning independently. Read the case study [here](/resource-center/trilith-studios-case-study). ## Progress From Individual to Team to Organization **Phase 1: Individual Productivity (Weeks 1-4)** Start with tools that make individual contributors more effective without requiring team coordination. AI writing assistants, data analysis tools, research acceleration. This phase builds confidence and demonstrates value without disrupting team workflows. **Phase 2: Team-Level Automation (Months 2-4)** Once individuals are comfortable, introduce automations that improve team workflows. Automated report generation, intelligent inquiry routing, collaborative AI-assisted documentation. This requires some coordination but delivers compounding value. **Phase 3: Organizational Transformation (Months 4-8+)** Only after individuals and teams have built AI competency should you tackle organization-wide systems. Most companies try to jump straight to Phase 3 and wonder why adoption fails. You can't transform organizationally until people have personal experience that AI works. ## Make Failure Safe and Learning Expected Your team won't adopt AI if they're afraid of looking stupid or breaking something important. Create explicit permission for experimentation. Make it clear that trying AI approaches that don't work is expected. Some AI suggestions will be terrible. Some automation attempts will fail. That's part of learning. One team we worked with created a Slack channel specifically for "AI failures"—people shared what didn't work and why. It was hugely valuable because it prevented others from making the same mistakes and normalized the learning process. ## Measure Progress, Not Just Activity Don't measure AI adoption by how many people have accounts or how often they log in. Measure actual impact: - **Time savings on specific tasks**: "This report used to take 4 hours, now takes 30 minutes" - **Throughput improvements**: "We're processing 40% more customer inquiries with the same team" - **Quality increases**: "Error rates dropped by 60% with AI-assisted review" - **New capabilities**: "We can now analyze customer sentiment in real-time" And critically, measure sentiment. Are people finding AI helpful, or are they using it because they have to? Genuine enthusiasm is a leading indicator. ## The Integration Challenge The hardest part of AI adoption isn't learning the tools—it's integrating them into existing workflows. Your team has established processes, tools they already use, and habits developed over years. AI adoption fails when it requires abandoning everything they know. The solution is meeting people where they are. If your team lives in Slack, integrate AI there. If they work primarily in spreadsheets, teach them AI tools that enhance spreadsheet work rather than replacing it. Adoption accelerates when AI enhances existing workflows rather than requiring entirely new ones. ## What Success Actually Looks Like Six months into effective AI adoption, you should see: **Organic spread**: People sharing AI techniques without being asked. **Sophisticated applications**: Teams moving beyond basic use cases to creative applications specific to your business. **Reduced support dependency**: People solving their own AI challenges rather than constantly asking for help. **Business impact**: Measurable improvements in speed, quality, capacity, or capability. **Cultural shift**: AI consideration becoming default in problem-solving. ## The Timeline Reality Organizations that adopt AI effectively typically see: - **Weeks 1-4**: Building individual confidence through low-risk experimentation - **Months 2-3**: First meaningful team-level automations showing measurable value - **Months 4-6**: Broader adoption as success stories spread organically - **Months 6-12**: Transformation of core processes with demonstrable ROI This isn't fast enough for executives who want instant transformation. But it's realistic, and it works. ## Start Small, But Start Now The biggest risk isn't starting with too small a scope—it's not starting at all. Pick one team. Identify one painful, repetitive process. Implement one AI solution that makes a real difference. Demonstrate clear value. Then expand from there. Your competitors are doing this right now. Some are further along than you think. The advantage goes to whoever builds organizational AI capability first, not whoever has the most ambitious AI strategy deck. --- ## https://www.buildfm.com/resource-center/the-roi-of-ai # Building Measurable ROI from Artificial Intelligence in 2025 ## A practical roadmap for SMB leaders ready to transform their operations In 2025, artificial intelligence has crossed a critical threshold. It's no longer experimental technology reserved for tech giants—it's an operational necessity for businesses of every size. Yet a striking paradox has emerged: while [a majority](https://colorwhistle.com/artificial-intelligence-statistics-for-small-business/) of small and medium businesses now use AI regularly, [only 5%](https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf) report measurable returns on their investment. This isn't a technology problem. It's a strategy problem. The companies generating millions in AI-driven value aren't using secret tools or advanced platforms. They're using the same accessible technology available to everyone. The difference? They understand that AI success requires more than adding software to existing processes. It requires [reimagining how work gets done](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai). ## The True Cost of Waiting The competitive landscape has fundamentally shifted. While 60% of large firms have integrated AI into their operations, only 41% of small firms have made the leap ([arxiv.org](https://arxiv.org/html/2509.14532v1)). This gap isn't just a statistic—it's a compounding disadvantage that grows wider every quarter. Consider what's happening in your market today: Companies that have successfully adopted AI are: - Saving 20+ hours per employee monthly - Reducing operational costs by 30% - Boosting marketing ROI by 32% - Increasing customer lifetime value by 20-30% - Reporting direct revenue growth in 91% of cases The global AI market, now [valued at $371.71 billion, is growing at 30.6% annually](https://www.marketsandmarkets.com/Market-Reports/artificial-intelligence-market-74851580.html). This explosive growth has democratized access to powerful tools. The technology is no longer the barrier. The question is whether you're ready to use it effectively. ## Why Most AI Initiatives Fail After working with multiple businesses, we've identified a critical pattern: companies stuck in "pilot purgatory" make the same fundamental error. They treat AI as a plug-and-play solution rather than a catalyst for organizational transformation. Only 21% of companies using AI have redesigned their workflows to maximize its potential. This single statistic explains the gap between success and failure. The 95% seeing no returns are those who automated broken processes and expected different results. The successful 5% rebuilt their workflows from the ground up, then deployed AI to power this new approach. Research from McKinsey and PwC confirms this pattern: high-performing companies are twice as likely to realize value from AI because they're willing to reengineer their processes. Even Gartner's [2025 Hype Cycle](https://www.gartner.com/en/articles/hype-cycle-for-artificial-intelligence) places generative AI in the "Trough of Disillusionment"—not because the technology fails, but because most organizations haven't done the necessary integration work. This creates an opportunity. While larger competitors struggle with bureaucratic inertia, agile SMBs can move quickly to capture value. ## Building Your ROI Framework Every successful AI investment starts with clear success metrics. Not vague aspirations, but specific, measurable outcomes tied to business value. Your framework should capture two categories of benefits: **Quantifiable Returns:** - Labor cost reduction through automation - Material savings from optimized operations - Direct revenue increases from enhanced capabilities - Measurable productivity gains **Strategic Value:** - Accelerated decision-making - Enhanced market positioning - Improved talent retention - Increased organizational agility Evaluate AI impact across four dimensions: 1. **Operational efficiency**: Direct cost savings and productivity improvements 2. **Risk mitigation**: Error reduction, compliance enhancement, security improvements 3. **Strategic capabilities**: New competencies that weren't previously possible 4. **Growth acceleration**: Revenue expansion and market opportunities Remember: AI systems improve over time. A tool delivering modest returns in month six might generate exponential value by year two as your team masters its capabilities and refines supporting processes. ## Real-World Success Metrics Let's examine concrete outcomes from companies that have crossed the AI divide: **Customer Economics Revolution:** One documented case improved their customer acquisition cost to lifetime value ratio from 1:3 to 1:6.4. AI-powered personalization consistently increases engagement by 40-60% and lifetime value by 20-30%. **Productivity Transformation:** Sales teams save 2 hours and 15 minutes daily per representative. Across all functions, businesses report 20+ hours saved monthly per employee—time redirected to strategic, growth-driving work. **Quality Breakthrough:** - Accounting errors reduced by 40% - Manufacturing defects decreased by 40-60% - Invoice processing accuracy reaching 90-95% **Revenue Acceleration:** Companies using AI across [three or more marketing functions](https://sqmagazine.co.uk/ai-in-marketing-statistics/) report 32% higher ROI. AI personalization drives 31% of e-commerce revenue. Every dollar invested in AI generates $4.90 in broader economic value. These aren't isolated wins—they compound. A 24% increase in organic traffic combines with a 16% reduction in stockouts to create a virtuous cycle where efficiency funds innovation, improving customer experience, generating better data, training superior AI, and further boosting efficiency. ## High-Impact Starting Points The 2025 AI landscape offers proven applications for virtually every business function. Here's where companies see the fastest returns: ### Customer-Facing Excellence **Marketing Transformation:** - 47% use AI for precision advertising - 46% deploy personalized content systems - 64% leverage ChatGPT for content creation - Results: 50%+ increase in qualified leads, 25% conversion rate improvement **Sales Acceleration:** - Intelligent lead scoring and prioritization - Personalized outreach at scale - Administrative task automation - Results: 2+ hours saved daily per rep, dramatic pipeline velocity increase **Service Revolution:** - 80% of SMBs deploy AI chatbots - 70-80% of routine inquiries handled automatically - Results: 30% satisfaction improvement, 20% retention increase ### Operational Excellence **Financial Operations:** - Automated invoice processing (90-95% accuracy) - Intelligent fraud detection - Predictive cash flow management - 28% of CFOs actively using, 39% planning adoption **Human Resources:** - Automated resume screening - Streamlined onboarding (2-3 hours saved per hire) - Predictive workforce analytics - 599% surge in HR automation adoption ### Industry-Specific Breakthroughs **Retail:** [ASOS](https://engipulse.com/business/retail-ai-revolution-case-studies-driving-2025-success/) achieved 253% profit growth through AI-driven personalization and logistics optimization. Walmart reduced stockouts by 16% using AI-powered shelf monitoring. **Manufacturing:** [15-25% improvement](https://hypestudio.org/ai-automation-roi-business-impact-the-complete-guide-2025/) in equipment effectivenessthrough predictive maintenance. [30-50% cycle time reduction](https://hypestudio.org/ai-automation-roi-business-impact-the-complete-guide-2025/) via intelligent production scheduling. **Professional Services:** [65-82% adoption](https://www.firmwise.io/post/ai-professional-services-2025) across service sectors, with 77% reporting improved efficiency, 74% seeing productivity gains, and 72% noting enhanced client satisfaction. ## Overcoming Real Obstacles Success requires acknowledging and addressing genuine challenges: **The Expertise Challenge:** 35% of businesses cite knowledge gaps as their primary barrier. The solution isn't competing for scarce AI talent—it's strategic partnership. Seventy percent of mid-market companies acknowledge needing external expertise. Embrace this reality and build the right partnerships. **Data Readiness:** 57% of organizations lack "AI-ready" data. Rather than launching massive data modernization projects, focus narrowly: identify your highest-value use case and prepare only the data it requires. Build from success. **Change Leadership:** Technical implementation is straightforward. Human adaptation is complex. Counter fears with facts: 82% of SMBs that adopted AI saw workforce growth, not reduction. The World Economic Forum projects AI will create 97 million new jobs while eliminating 85 million. Communicate this narrative consistently. **Governance Foundation:** As AI assumes greater decision-making responsibility, governance becomes critical. Build responsible AI practices from day one, not as an afterthought. This protects against bias, ensures compliance, and maintains customer trust. ## The Portfolio Strategy Structure your AI investment across three strategic tiers: **Foundation (Immediate Impact):** Deploy proven tools across multiple functions. Customer service chatbots, marketing optimization, financial automation. These generate quick returns, build confidence, and fund deeper initiatives. **Transformation (Strategic Advantage):** Select 1-2 core processes for fundamental redesign. Predictive inventory management, AI-powered customer intelligence, or autonomous quality control. These create sustainable competitive differentiation. **Innovation (Market Leadership):** Reserve capacity for one high-risk, high-reward initiative that could redefine your business model. This requires C-suite championship and alignment with your long-term vision. This portfolio creates a self-funding cycle: quick wins generate capital and credibility for strategic projects, which establish the foundation for transformative innovations. ## Leadership's Critical Role The evidence is clear: [direct CEO involvement in AI strategy](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) correlates most strongly with positive outcomes. This cannot be delegated as an IT project. It must be championed as strategic transformation. Your leadership responsibilities: 1. **Define the vision**: Set ambitious, specific goals for AI's role in your business 2. **Enable success**: Invest in training, encourage experimentation, model new approaches 3. **Maintain focus**: Resist dispersing efforts. Concentrate on highest-value opportunities Winners aren't those with the most sophisticated AI—they're those with the clearest strategy and strongest execution. ## The Approaching Revolution The next wave is already forming. "Agentic AI"—systems that independently plan and execute complex workflows—represents the next frontier. Seventy-three percent of executives expect significant competitive advantage within twelve months. [PwC](https://www.pwc.com/us/en/tech-effect/ai-analytics/ai-predictions.html) predicts these AI agents could effectively double operational capacity. [Gartner](https://www.zdnet.com/article/ai-will-handle-half-of-all-business-decisions-by-2027-gartner-report/) forecasts that by 2027, they'll automate or augment half of all business decisions. For SMBs, this presents unprecedented opportunity: scalable growth without proportional overhead increases. The businesses positioned to harness this power are those building foundations today. ## Your Action Plan The AI divide is widening. The cost of inaction now exceeds the risk of thoughtful investment. Here's how to begin: **Next 30 Days:** - Identify 2-3 high-impact processes for AI enhancement - Assess data readiness for these specific processes - Establish clear, measurable success metrics **Next 90 Days:** - Deploy 1-2 proven AI tools for quick wins - Establish governance framework - Launch your first strategic AI project **Next Year:** - Scale successful implementations across the organization - Complete your strategic transformation project - Build the case for your innovation initiative ## The Decision Point The companies thriving in 2025 and beyond won't be those with the largest budgets or most advanced technology. They'll be those with clear vision, disciplined execution, and courage to fundamentally rethink value creation. The tools are accessible. The use cases are proven. The returns are measurable and substantial. The time for decision is now. --- *Ready to build your AI roadmap? [Contact us](/get-started) to learn how FM can help you cross the AI divide and unlock transformational ROI for your business.* --- ## https://www.buildfm.com/resource-center/identifying-automation-candidates # Identifying Which Processes Are Best Candidates for Automation "We want to implement automation, but we're not sure where to start. Everything feels like it could be automated, but we don't want to waste time and money on the wrong things." Smart concern. Not every process should be automated, and the order matters enormously. Automate the wrong process first, and you'll invest significant resources for minimal impact—killing momentum for broader automation initiatives. Automate the right process first, and you'll demonstrate clear value quickly, creating appetite for more automation. Here's how to identify your best automation candidates. ## Start With the Time Investment Calculation The simplest first filter: how much time does this process consume? **Formula: Frequency × Duration = Total Time Investment** Example: - Process: Manual data entry for customer orders - Frequency: 40 orders daily - Duration: 15 minutes per order - **Total: 10 hours daily = 50 hours weekly = 2,600 hours annually** At $35/hour loaded cost: $91,000 annual labor cost for this one process. Now that's an automation candidate worth investigating. Do this calculation for every repetitive process your team handles. You'll quickly identify the top 10-15 time consumers—your initial candidate pool. ### The Hidden Time Costs Don't forget to include follow-up work when initial process has errors, coordination time between people handling different steps, status update meetings about the process, and management time reviewing outputs. A client thought invoice processing took 20 minutes per invoice. When they included error correction, approval routing, and status tracking, actual time was 47 minutes per invoice. That difference—20 vs 47 minutes—dramatically changes ROI calculations. ## Evaluate Against the Automation Suitability Criteria Not all high-volume processes are good automation candidates. Filter your list using these criteria: ### Rule-Based vs. Judgment-Based **Good for automation:** Processes that follow consistent, predictable rules - "If order total > $10,000, route to senior approver" - "Extract invoice date, vendor name, amount, and line items" - "Send reminder emails 7 days, 3 days, and 1 day before deadline" **Challenging for automation:** Processes requiring nuanced judgment - "Evaluate whether this customer complaint requires escalation" - "Determine appropriate tone for response based on customer relationship" Note: intelligent automation with AI can handle some judgment-based processes, but rule-based processes are easier, cheaper, and less risky to automate. Start there. ### Consistency and Standardization **Good for automation:** Processes that work the same way every time - Weekly report generation following same steps - New employee onboarding with defined workflow - Order fulfillment with standard steps **Challenging for automation:** Processes with high variation - Customer requests that each require custom handling - Problems that require different solutions based on unique circumstances The more consistent and standardized the process, the easier and cheaper to automate. ### Volume and Frequency **High priority:** High-volume, frequent processes - 100+ customer inquiries daily - Hourly data synchronization between systems - Daily report generation **Lower priority:** Low-volume, infrequent processes - Quarterly board reports (4 times annually) - Annual performance reviews Automation requires upfront investment. High-volume processes generate faster ROI because savings compound with each execution. ### Error Rates and Cost of Errors **High priority:** Processes with high error rates or expensive error consequences - Manual data entry with 5-8% error rate requiring costly correction - Compliance processes where errors create regulatory risk - Financial transactions where errors cost real money Automation often reduces error rates to near zero—particularly valuable when errors are expensive. A financial services client had 3.2% error rate in manual insurance claims processing. Average error required 90 minutes to identify and correct. At 500 claims weekly: 16 errors × 90 minutes × 52 weeks = 1,248 hours annually spent fixing errors. Automation reduced error rate to 0.2%, saving ~1,150 hours annually just in error correction, plus the actual cost of errors themselves. ## Look for These High-Value Automation Patterns Certain types of processes consistently deliver strong automation ROI: ### Data Entry and Transfer Moving information from one system to another, or from documents into systems, is perfect for automation. Why good candidates: Rule-based, high volume, error-prone when manual. ### Report Generation Pulling data from systems, formatting it, and distributing to stakeholders. Why good candidates: Highly repetitive, time-consuming, follows consistent format. ### Email and Communication Routing Reading communications, determining appropriate routing, and directing to correct person or team. Why good candidates: High volume, pattern-based, can use intelligent automation for context understanding. ### Data Validation and Quality Control Checking data against rules to ensure accuracy and completeness. Why good candidates: Rule-based, catches errors before they compound, reduces downstream work. ### Scheduled Tasks and Notifications Actions that need to happen at specific times or intervals. Why good candidates: Perfectly consistent, easy to automate, eliminates human forgetting. ## Identify Processes Currently Creating Bottlenecks Look for where work queues up and creates delays: "Why is there always a 3-day backlog in invoice processing?" "Why do approval requests sit for days before someone reviews them?" "Why can't we respond to customer inquiries same-day?" Bottlenecks indicate capacity constraints—either you don't have enough people for the volume, or the process is inefficient. Automation can eliminate bottlenecks by handling volume faster than humans can, operating 24/7 without breaks. A client had 2-day average response time to customer inquiries because their 4-person support team couldn't keep up with volume. Automating tier-1 inquiries dropped average response time to 4 hours—and freed support team to focus on complex issues requiring human expertise. ## Talk to Your Team About Frustrations Your people know which processes are painful. Ask: "What tasks feel like a waste of your time?" "What do you spend significant time on that feels like it should be automated?" "What processes are frustrating because they're repetitive and monotonous?" The processes that frustrate people most are often prime automation candidates: repetitive enough to be boring, time-consuming enough to be annoying, obvious enough to be memorable. Bonus: automating the processes that frustrate your team improves morale and retention—people appreciate when you eliminate their most tedious work. ## Calculate Potential ROI Before Committing Once you've identified promising candidates, estimate ROI: ### Time Savings Value Current annual hours × Loaded hourly cost × Percentage reduction Example: - 2,600 hours annually × $35/hour × 80% reduction = $72,800 annual savings ### Error Reduction Value Current error rate × Cost per error × Volume × Reduction percentage Example: - 5% error rate × $125 per error × 10,000 transactions × 90% reduction = $56,250 annual savings ### Compare Against Automation Investment If annual value significantly exceeds automation investment, it's a strong candidate. **Example:** - Annual value: $72,800 (time savings) + $56,250 (error reduction) = $129,050 - Automation investment: $35,000 (implementation) + $6,000 (annual maintenance) = $41,000 year 1 - **Year 1 ROI: 215%** - **Payback period: 3.8 months** That's a no-brainer automation candidate. ## Start With Quick Wins, Then Tackle Complex Opportunities Your first automation should demonstrate clear, fast value: **Good first automation:** - Well-defined process - Clear ROI - Relatively simple to implement - 4-8 weeks to deploy - Delivers measurable results immediately **Bad first automation:** - Ambiguous requirements - Complex cross-department workflow - Requires extensive integration - 6-month project timeline - Value only materializes after full completion You need early wins to build organizational confidence in automation. Start with straightforward, high-ROI processes. Use that success to justify tackling more complex automations later. ## The Prioritization Framework That Works Score each candidate process across these dimensions (1-5 scale): 1. **Time Investment:** How much time does this consume? (5 = massive time sink) 2. **Consistency:** How standardized is the process? (5 = identical every time) 3. **Volume:** How frequently does this happen? (5 = constantly) 4. **Error Rate/Impact:** How problematic are errors? (5 = costly/common errors) 5. **Implementation Complexity:** How hard to automate? (5 = simple, 1 = very complex) 6. **Strategic Value:** How important to business goals? (5 = critical enabler) **Priority Score = (Time + Consistency + Volume + Error + Strategic) - Complexity** Higher scores = better candidates. This framework helps you compare across different process types objectively rather than relying on gut feel. ## The Bottom Line Not every process should be automated, and starting with the wrong process can doom your automation initiative. Best automation candidates have: - High time investment (volume × duration) - Rule-based, consistent processes - High frequency - Significant error rates or expensive errors - Clear ROI that justifies investment - Strategic importance to business goals Start with quick wins that demonstrate value fast. Use success to build confidence and secure investment for more complex automation opportunities. Identify your top 3-5 automation candidates. Calculate actual ROI. Start with the highest-value, lowest-complexity option. Demonstrate results. Then scale from there. That's how you build an automation program that delivers compound value rather than becomes an expensive experiment that fizzles after the first project. --- ## https://www.buildfm.com/resource-center/from-prompt-to-product # From Prompt to Product ## The New Digital Product Workflows FM is excited to announce our upcoming hands-on workshop for digital product design and development professionals. Join us on **[November 5th at Atlanta Tech Village in Buckhead](https://www.meetup.com/tyrannosaurus-tech-atlanta/events/311185063/)** for a day of learning, networking, and hands-on experience with the latest tools and techniques for building digital products. FM is co-sponsoring this event with [Tyrannosaurus Tech](https://tyrannosaurustech.com) and we have brought in some of the brightest minds in the industry to share their knowledge and experience with you. ## About Your Instructors **Shannon Smith** is the Director of Business and Technical Operations at Tyrannosaurus Tech, where she leads AI strategy for internal operations and client offerings. As an entrepreneur and business strategist, Shannon has 10+ years of experience leading technical teams and building SaaS products for organizations including Amazon, Brightwell, Delta, Deloitte, Mailchimp, and Ron Clark Academy. **Drew Schillinger** is what happens when you mix 25 years of engineering with a refusal to stop learning. He spent 15 years at WarnerMedia building platforms for Adult Swim, NBA, and HBO, and now spends his time diving deep into applied AI – RAG, agentic systems, and beyond. Drew also moderates the r/RAG community and teaches AI camps, translating big, messy ideas into something people can actually use (and maybe even enjoy building). ## The Professional Approach to AI Development While many teams experiment with ad-hoc AI usage, industry leaders are establishing structured workflows that transform how products get built. This isn't about replacing your expertise—it's about amplifying it with AI that works the way professionals actually build. In this intensive workshop, you'll experience the complete development cycle in a single day. Product managers will discover how to create PRDs that engineering actually loves. Developers and architects will learn to leverage AI for rapid prototyping without sacrificing code quality. Everyone will master the collaborative workflows that are redefining how products get built. ## Details * November 5th from 10am to 4pm * Hands-on workshop (bring your laptop!) * Lunch and refreshments provided * Ticket purchase required ($199) * Early bird discount available **[Register Now](https://www.meetup.com/tyrannosaurus-tech-atlanta/events/311185063/)** ## Join the Virtuosos Community If these types of events are important to you, consider joining the [Virtuosos](https://virtuosos.dev) community, where we are building a network of like-minded professionals dedicated to advancing the state of AI and digital product development. --- ## https://www.buildfm.com/resource-center/trilith-studios-case-study # How Trilith Studios Empowered Their Team with AI: A Workshop Case Study **Transforming a "small and mighty" team into AI thought leaders through hands-on, interactive training** ## The Challenge: Doing More with Less Trilith Studios operates one of the most impressive production facilities in the entertainment industry. Spanning over 700 acres in Atlanta, Georgia, the studio provides everything filmmakers need—from 29+ production stages to on-site accommodations, from backlots to wellness centers. It's a filmmaker's destination where major Marvel productions, theatrical films, and television shows come to life. But behind this massive operation is what their team calls a "small and mighty" group of professionals. "We like to refer to our studio team as small and mighty, so we're not a very big team," explains Tracy Cronin, Chief of Staff at Trilith Studios. "Which means team members take on various cross-functional roles to really ensure that Trilith is truly a place that has every resource storytellers need to make anything they can imagine." **The reality of running a world-class studio with a lean team meant everyone wore multiple hats.** Marketing specialists handled operations. Production coordinators managed communications. Operations leads contributed to business development. It was exactly the kind of environment where AI tools could make a significant impact—if the team knew how to use them effectively. "We recognized that leveraging AI tools in our workplace would be a super important component when it comes to ensuring our team is able to manage all of their cross-functional roles and contribute to our studio operations," Cronin shared. This recognition wasn't just coming from the operations team—it was a strategic mandate from the very top. **Dan T. Cathy, Trilith's Chief Visionary and owner of Chick-fil-A, understood that AI adoption would be critical to the studio's future success.** His vision set the tone for what would become a transformational initiative for the entire organization. The question wasn't whether to adopt AI. It was how to do it effectively, across different teams with different working styles and organizational structures. ## The FM Approach: Listening, Adapting, Delivering Trilith Studios came to FM with ambitious ideas about implementing AI across their organization. They needed more than generic training—they needed something tailored to their unique needs, budget, and diverse team structures. "The FM team was absolutely amazing to work with," Cronin recalls. "We came to FM with really big ideas about how we wanted to see AI in action across all of our different organizations. The team really listened to our needs and were able to work within our budget to translate our really big ideas into smaller areas of focus." ### Collaborative Planning Rather than presenting a one-size-fits-all solution, FM worked closely with Trilith to understand: - The specific roles and responsibilities of different teams - The daily workflows that could benefit most from AI - The varying levels of technical comfort across the organization - Budget constraints and desired outcomes - The need for practical, immediately applicable skills "I think the biggest impact of working with FM was not only their organization and execution, but their access to this really wide network of AI professionals that they then activated according to our workshop needs to ensure that we were bringing in subject matter experts who would make the biggest impact during our workshop." ### Strategic Focus Areas Through this collaborative process, FM and Trilith identified three core areas that would deliver the most value: 1. **Mastering Prompting** - Teaching teams how to communicate effectively with AI tools to get better results 2. **Improving Meeting Efficiencies** - Using AI to streamline planning, documentation, and follow-up 3. **Generating High-Quality Presentations** - Leveraging AI to create compelling visual content faster All of this was framed around a central theme: **how AI is shaping productivity in the modern workplace.** ## The Workshop: AI in Action When workshop day arrived, the FM team came prepared with a detailed plan to maximize every minute of the engagement. And the Trilith team was ready to learn, including Dan T. Cathy, who joined to introduce the FM team and share his vision for AI adoption at Trilith Studios. Dan stayed throughout the session, learning alongside his team. ### Interactive and Hands-On "The AI in Action workshop was perfectly executed by the FM team," Cronin explains. "They showed up with a plan for how to maximize our time together. They had slides prepared to help walk our teams through how to use these AI productivity tools." But the real magic wasn't in the slides—it was in the approach. "The biggest impact of our workshop was the fact that it was interactive and hands-on. It gave our teams a chance to see in real time how to use certain AI tools and relate them to productivity in their individual roles." Rather than sitting through lectures about AI theory or watching demonstrations, Trilith's team members worked directly with AI tools during the session. They brought their actual work challenges into the workshop and learned to solve them using AI assistance. ### The Energy Shift About halfway through the workshop, something remarkable happened. "At one point during our workshop, I looked around the room and you could feel this energy and excitement as you started to see team members learning about how functional these AI productivity tools can be in their individual jobs." Team members weren't just learning abstract concepts—they were having genuine "aha" moments as they discovered how AI could transform their daily work. "In between our individual sessions, I would have team members come up to me and share what they had just learned and the immediate application to their role, to their job, and how it's going to improve what they're working on." ### Real-World Application The workshop wasn't designed to create AI experts overnight. It was designed to give team members the confidence and skills to start using AI tools immediately in their specific roles. - The marketing team learned how to use AI for content creation and campaign planning - Operations staff discovered ways to automate routine documentation - Production coordinators found tools to streamline scheduling and communication - Leadership saw opportunities to enhance strategic planning and reporting Each team member left with practical skills they could apply the very next day. ## The Transformation: From Novices to Thought Leaders The impact of the workshop extended far beyond the day itself. "By the end of our workshop, our teams left feeling educated and empowered to use AI tools to increase productivity in their roles," Cronin shares. "We had teams go from not using AI at all to now being some of the thought leaders in our organization when it comes to how we can leverage AI tools to increase our productivity." ### Immediate Adoption Unlike many training programs where knowledge slowly fades after the session ends, Trilith's team members immediately began applying what they learned. The hands-on nature of the workshop meant they already had experience using the tools by the time they returned to their desks. ### Cultural Shift Perhaps more importantly, the workshop shifted how the organization thought about AI. "It was really amazing to see this shift in mindset across our team," she explains. "And we're so thankful we found such a valuable resource in FM to make all of this possible." AI went from an intimidating, abstract concept to a practical set of tools that could help them do their jobs better. Team members who had been hesitant about AI became advocates for its adoption. Those who had experimented on their own found new techniques and best practices. ### Ongoing Impact Months after the workshop, the cultural change continues. Team members regularly share AI tips and tricks with each other. They've integrated AI tools into standard workflows. And most importantly, they've maintained the excitement and curiosity that sparked during that initial workshop. ## Lessons for Other Organizations Trilith Studios' experience offers valuable insights for other businesses considering AI adoption: ### 1. Start with People, Not Technology The most successful AI implementations begin with understanding your team's needs, not with selecting tools. FM worked with Trilith to identify the specific challenges their teams faced before recommending any solutions. ### 2. Make It Hands-On Watching demonstrations isn't the same as doing. Trilith's team learned best by actually using AI tools during the workshop with their own work scenarios. ### 3. Tailor to Your Context Generic AI training rarely sticks because it doesn't connect to real work. By focusing on Trilith's specific use cases—from studio operations to creative production—the training was immediately relevant. ### 4. Work Within Reality FM helped Trilith translate "really big ideas into smaller areas of focus" that fit their budget and timeline while still delivering significant value. ### 5. Energy Is Contagious When a few team members get excited about AI's possibilities, that enthusiasm spreads throughout the organization naturally. ## A Message to Other Businesses Cronin had this advice for other organizations considering AI adoption: "I would tell other businesses who are hesitant or unsure about how to use AI in their workplace to definitely partner with FM to educate their teams on the full scope and range of what AI can do. FM will be your biggest ally and resource when it comes to adapting your business to meet the rapid advances in all of the AI capabilities." She continued: "They're a thought leader in the AI space and they bring all the tools, resources, and knowledge to the table. So all your team has to do is show up and prepare to have their minds blown when they learn about all that AI can do in the workplace." ## The Bigger Picture: Making AI Accessible What makes Trilith Studios' story particularly powerful is how it demonstrates that successful AI adoption doesn't require massive budgets, large IT departments, or months of implementation. A single day of focused, practical, hands-on training transformed how an entire organization approaches their work. This is the democratization of AI in action. Not AI as a replacement for human creativity and expertise, but as a tool that amplifies what talented people can accomplish—especially when those talented people are wearing multiple hats and managing cross-functional responsibilities. For organizations wondering if their team is "ready" for AI, Trilith's experience suggests a different question: **Can your team afford not to leverage tools that could dramatically increase their productivity and impact?** --- ## Ready to Transform Your Team? If you're looking to educate and empower your team to use AI tools effectively, FM's **Business is Software Workshop** can help you identify opportunities and build capabilities tailored to your organization's unique needs. **[Get Started](/get-started)** or **[Learn More About Our Workshops](/solutions)** --- ## About Trilith Studios Trilith Studios is a premier film and television production facility spanning over 700 acres in Atlanta, Georgia. With 29+ production stages, on-site accommodations, and comprehensive production services, Trilith serves as a complete creative destination for storytellers. The studio has hosted major productions including Marvel films, theatrical releases, and television series. Learn more at [trilithstudios.com](https://trilithstudios.com). --- ## https://www.buildfm.com/resource-center/forward-deployed-engineers # How Do Forward-Deployed Engineers Differ from Traditional Consultants? A client once told me: "We paid consultants $80,000 for a three-month engagement. We got a beautiful 120-slide presentation recommending what we should build. Then they left, and we still had to find someone to build it." That's traditional consulting: analysis, recommendations, and a handoff. Forward-deployed engineers work completely differently. ## Traditional Consultants: The Observe-Recommend-Exit Model Here's the typical consulting engagement: **Week 1-4:** Consultants interview your team, observe operations, gather requirements, analyze workflows. **Week 5-10:** They disappear into conference rooms to synthesize findings and create recommendations. **Week 11-12:** They present elaborate findings with strategic recommendations, implementation roadmaps, and technology evaluations. **Week 13:** They leave. **Week 14+:** You're left with a deck and the question: "Now what?" The deliverable is documentation and recommendations. Implementation? That's your problem. Or they'll happily sell you another engagement to "oversee implementation"—which usually means managing other people who are doing the actual work. ## Forward-Deployed Engineers: The Embed-Build-Solve Model Forward-deployed engineers work alongside your team from day one, writing code and solving problems in real-time. **Day 1:** They're in your environment (physically or virtually), understanding your context by working with your team. **Week 1:** They've already identified quick wins and possibly implemented them. **Week 2-4:** They're building prototypes, making architectural decisions, writing code—not documenting recommendations. **Throughout:** They're transferring knowledge by doing, not through separate training sessions. **Outcome:** Working software that solves business problems, plus your team has learned by collaborating rather than reading documents. The deliverable is solutions, not recommendations. ## Doing Versus Advising This is the fundamental difference. Traditional consultants: "Based on our analysis, you should build an API integration between these systems using this architecture. Here's why, here are the considerations, here's a recommended approach." Forward-deployed engineers: [Actually builds the API integration while collaborating with your team] One produces recommendations to implement later. The other produces working solutions now. A financial services client had hired strategy consultants who recommended modernizing their client onboarding system. Recommendations were sound—but generic enough to apply to any similar company. Implementation would require finding developers who understand the recommendations, translating business recommendations into technical specifications, building the system, and hoping the consultants' recommendations hold up when confronted with real technical constraints. Instead, they brought in forward-deployed engineers who spent the same time budget building the new onboarding system—discovering and solving real challenges as they arose rather than theorizing about them in presentations. Result: working system in the same time and budget that consultants spent producing recommendations. ## Knowledge Transfer Through Doing Traditional consulting often includes "knowledge transfer" as a phase: presentations, documentation, maybe training sessions where consultants explain their recommendations. Forward-deployed engineers transfer knowledge through collaboration. Your team works alongside them, sees how decisions get made, understands tradeoffs directly, and learns patterns they can apply independently. Example: A consultant might recommend: "Implement caching to improve API performance. Here are three caching strategies with pros and cons." A forward-deployed engineer: [Implements caching while explaining decisions to your team] "I'm using Redis here instead of application-level caching because your load pattern has these characteristics. See how we're invalidating cache on updates? This pattern will work for other features too. Let me show you..." One approach delivers a recommendation. The other delivers working code plus team members who understand caching well enough to implement it elsewhere. A developer from one client told me: "I learned more about system architecture in two months working with your team than in two years reading about it. Because I was making decisions on actual problems, not theoretical examples." ## Accountability for Outcomes Traditional consultants are accountable for the quality of their recommendations and analysis. Whether those recommendations solve your problem? That's harder to measure, and by the time you find out, they're gone. Forward-deployed engineers are accountable for working software that solves business problems. The software either works or it doesn't. It either delivers value or it doesn't. This accountability difference changes everything about the engagement. If a consultant's recommendation turns out wrong when you try to implement it, that's your problem—they delivered what they were contracted to deliver (recommendations). If a forward-deployed engineer's code doesn't solve the problem, that's their problem—they haven't delivered what they were contracted to deliver (solutions). ## The Interaction Model ### Traditional Consulting **Your experience:** Scheduled interviews where you explain your situation. Maybe workshops where consultants gather input. Long periods where you don't know what they're working on. Presentations where findings are revealed. **Consultant experience:** Observation, analysis, synthesis, presentation. Limited hands-on interaction with actual systems or day-to-day operations. ### Forward-Deployed Engineering **Your experience:** Collaborative working sessions. Watching solutions take shape in real-time. Providing feedback on actual software rather than abstract concepts. Daily visibility into what's being built. **Engineer experience:** Writing code, making decisions, building infrastructure, integrating systems—solving problems rather than documenting them. The interaction isn't "we analyze, you wait, we present." It's "we work together to solve this, here's what we're building, what do you think?" ## Speed to Value Traditional consulting engagements often take months before any value materializes—because value only comes when you successfully implement their recommendations. Forward-deployed engineers deliver value as they work. Week 2 might include quick wins that solve immediate problems. Week 4 brings working prototypes. Week 8 delivers production-ready capabilities. A manufacturing client was frustrated by slow response from traditional IT consultants. Every change required new assessment, new proposals, new approval cycles. Forward-deployed engineers embedded with their operations team could respond to needs immediately: "This workflow is painful? Let me fix it today. Here's the change, test it, we'll refine based on feedback." They valued this responsiveness more than perfect solutions that took months to deliver. ## The Cost Structure Traditional consulting often charges for time spent analyzing and recommending, then separately for implementation (either their people overseeing your implementation or a whole new engagement). Forward-deployed engineers charge for building solutions. You're paying for outcomes, not analysis. Cost comparison: - Traditional: $80K for recommendations + $150K-$200K for implementation = $230K-$280K - Forward-deployed: $160K-$180K for working solution You're not just saving money—you're compressing timeline and reducing translation loss between strategy and execution. ## When Traditional Consulting Still Makes Sense There are scenarios where traditional consulting is appropriate. **Pure strategy questions:** If you need help with market analysis, business model evaluation, or organizational design—problems where implementation isn't the bottleneck—traditional consulting fits. **Highly specialized expertise:** Sometimes you need specific domain knowledge for analysis without needing that person to implement. Example: regulatory compliance assessment, market research, specialized technical audits. **Stakeholder alignment:** Sometimes the value of consultants is providing outside perspective that helps internal stakeholders align—the recommendations matter less than the process of creating them. But for software development, system implementation, or technical problem-solving? Forward-deployed engineers almost always deliver better outcomes faster. ## What to Look for in Forward-Deployed Engineers Not everyone calling themselves "forward-deployed" works this way. Look for: ### Hands-On Technical Capability Can they write production-quality code? Make architectural decisions? Configure infrastructure? Or are they "technical advisors" who review what others build? Ask: "Walk me through a recent project where you personally wrote code. What technologies? What challenges?" ### Experience Making Real Decisions Have they built similar systems before? Can they make confident decisions about technical approaches without weeks of research? Ask: "How do you decide between competing technical approaches? Give me an example from a recent project." ### Collaborative Working Style Do they work alongside your team, or do they view your people as resources to manage? Ask: "How do you typically interact with client teams day-to-day? How do you handle when a client team member disagrees with your approach?" ### Commitment to Knowledge Transfer Are they invested in making your team more capable, or protective of their knowledge to ensure continued dependence? Ask: "How do you ensure our team can maintain and extend what you build after you're done?" ## The Bottom Line The gap between strategy and execution has killed more business initiatives than bad strategy ever did. Traditional consulting widens that gap—recommendations separate from implementation, strategy separate from execution, experts separate from people doing the work. Forward-deployed engineers collapse that gap—strategy emerges from building, recommendations become implementation, expertise transfers through collaboration. For software development and technical problem-solving, the forward-deployed model delivers: - Faster time to value (weeks instead of months) - Better alignment between strategy and execution (because they're the same thing) - Knowledge transfer that sticks (learning by doing) - Accountability for outcomes (working software, not just recommendations) - More cost-effective results (pay once for solutions, not twice for recommendations plus implementation) You don't need more presentations about what you should build. You need people who can build it. --- ## https://www.buildfm.com/resource-center/how-to-choose-an-ai-consultancy # How to Choose an AI Consultancy: A Buyer's Framework Most AI consultancy engagements that disappoint share a single root cause: the buyer didn't ask the right questions before signing. Every consultancy can show a polished deck and name-drop a few clients. The hard part is separating the firms that ship working systems from the firms that ship strategy memos and walk away. This is a working buyer's framework. A scoring rubric, the red flags to watch for, and a small set of questions that reveal what kind of partner you're really hiring. ## A scoring rubric for AI consultancies Score each candidate from 1 (worst case) to 5 (best case) across nine dimensions. Anything under 30/45 total is a real concern. Anything over 38 is a strong fit. | Criterion | 1 / 5 looks like | 5 / 5 looks like | | --- | --- | --- | | **Discovery vs. delivery balance** | 6–8 weeks of discovery before any code | 1–2 weeks of focused discovery, then a working prototype | | **What gets delivered** | A strategy deck and recommendations | Working software, deployed in your environment | | **Team seniority** | A PM fronting offshore juniors you never meet | Senior engineers doing the work directly, named on the contract | | **AI evaluation & quality** | "We'll test it before launch" | Custom eval suites and structured logging built in from day one | | **Model choice & vendor neutrality** | Locked into one provider regardless of fit | Claude, ChatGPT, Gemini evaluated per use case with clear rationale | | **Integration approach** | One-off custom integrations for every tool | MCP servers, reusable patterns, agents that reach into your systems cleanly | | **Code & IP ownership** | Licensed platform you must keep paying to access | You own every line of code, on your accounts, from day one | | **Ongoing maintenance** | Hand-off then unavailable | Optional retainer OR a clean handoff with real documentation | | **Risk transparency** | "Nothing should go wrong if you follow our process" | Names specific risks upfront with mitigation plans | ## Red flags to watch for Any one of these alone isn't disqualifying. Three or more is. - **"We're excited about AI."** Excitement isn't capability. Ask for specifics. - **Massive teams with unclear roles.** Usually means you're paying for layered management. - **AI as a buzzword.** No specific tools, frameworks, or model names mentioned. - **No mention of evaluation.** If they can't tell you how they know the AI is working in production, they don't know either. - **Vague code ownership.** "We'll work that out in the SOW" is a no. - **Hourly billing with no upper bound.** Outcomes-based pricing aligns incentives. Hourly does the opposite. - **No honest disqualifiers.** A consultancy that says it's right for every problem is right for none. ## Six questions that reveal posture The scoring rubric covers what to look for. These six questions tell you who you're actually dealing with. Ask all of them in a single conversation and pay attention to whether the answers are specific, honest, and grounded in real work. This separates the firms that build from the firms that talk. A good answer names a specific system, what it does, and how the client uses it. A bad answer is generic ("we recently helped a Fortune 500 client streamline their operations") or pivots into a deck. If they can't show you something running with users on it, the rest of the conversation doesn't matter much. Production AI is non-deterministic. The difference between a demo and a production system is whether you know when it breaks. A consultancy that can show you actual eval code, test cases, and logging dashboards is doing the work. A consultancy that can't is shipping demos that haven't been pressure-tested in front of real users yet. The honesty test. Every consultancy has projects that struggled. The ones that pretend otherwise are the dangerous ones. Listen for specifics, root-cause analysis, and what they changed in their process afterward. A partner that's open about past failures will be open about risks on your project too. A consultancy with no disqualifiers is a consultancy that says yes to everything for revenue. Listen for actual scope refusals — types of work, types of clients, types of engagements where they know they're not the right fit. The clearer the no, the more credible the yes. This catches the bait-and-switch where senior people pitch and junior people build. The right answer is "yes, here they are, let's set up a call this week." If the answer is "we'll introduce you after you sign the SOW," the people on the call aren't the people on the project. Reveals whether they're building for handoff or for lock-in. A good partner answers concretely — documentation your engineers can actually use, training sessions during the engagement, decision documents explaining why the system was built the way it was, and clean handover of accounts and credentials. A partner that hedges, or who immediately steers the answer toward "most clients keep us on a retainer," may be building something you'll struggle to operate independently. ## FAQ ### How long should I spend evaluating AI consultancies? For a 4–16 week engagement, two to four weeks of evaluation is reasonable. Talk to three partners minimum, score them against the rubric above, and ask each one a question you already know the answer to (to check whether they bluff or admit they don't know). ### What's a fair price range to expect? It depends on scope. As a rough frame: a focused 4–6 week AI adoption assessment usually runs in the low five figures. A 4–12 week agents and automations build usually runs in the mid five to low six figures. An 8–16 week custom software replatform usually runs in the mid-to-high six figures. Outcomes-based pricing should be the norm. Firms that quote hourly with no upper bound are a red flag. ### Should I run an RFP? RFPs are useful when you need to compare apples-to-apples on a well-scoped problem. They're counterproductive when you're still figuring out what to build — they reward partners who write good documents, not partners who build good software. For AI work, a paid two-week discovery engagement with one or two finalists usually tells you more than an RFP ever will. ### Should I ask for references? Yes. Ask each reference three specific questions: "What surprised you about working with this firm?", "What would you do differently?", and "Would you hire them again for a different project?" The third question is the most honest signal you'll get. ### What if my team isn't technical enough to evaluate AI-specific answers? Bring in an independent advisor for the evaluation conversations. A one-to-two hour consult with someone senior who has actually shipped AI systems will cost far less than picking the wrong consultancy. --- If you're looking for an AI consultancy that delivers working systems, where senior people do the work, and you own everything that gets shipped — [FM](/solutions) might be the right fit. Most engagements start with a 30-minute scoping call. No decks, no hard sell. --- ## https://www.buildfm.com/resource-center/what-makes-fm-different # FM vs. a Traditional Consultancy: An Honest Comparison The honest answer to "what makes FM different" is that FM is built around assumptions a traditional consultancy can't really adopt without taking themselves apart. Smaller, more senior, AI-first delivery, and outcomes-based pricing instead of hourly billing. That works extremely well for some engagements and not at all for others. This is the side-by-side comparison and, more usefully, when a traditional consultancy is the better fit. ## FM vs. a traditional consultancy | Dimension | Traditional consultancy | FM | | --- | --- | --- | | **Team composition** | Partners pitch, juniors deliver, project managers translate | Senior engineers and operators do the work directly — the people on the call are the people on the project | | **What gets delivered** | Strategy decks, recommendations, and follow-on engagements | Working software and systems running in your environment, with the documentation to operate them | | **AI in the engagement** | AI as a strategy offering or a marketing label | AI inside the build process, accelerating the work and shipped into the final system | | **Engagement length** | Months to years, with phased follow-ons | 4–16 weeks per build, designed to ship and stop | | **Pricing model** | Hourly billing with rate cards by role; scope expands over time | Outcomes-based pricing tied to milestones; the number is the number | | **Code & IP ownership** | Often licensed back to you, or locked into the consultancy's platform | You own every line of code, the data, and the deployment, from day one | | **Post-launch** | Ongoing retainers and staff augmentation by default | Optional maintenance retainer OR a clean handoff with real documentation | | **What they refuse to take on** | Rarely a "no" if the budget is there | Explicit disqualifiers (staff augmentation, deck-only advisory, lock-in platforms, domains FM doesn't actually know) | ## When a traditional consultancy is the better fit FM is not the right partner for every engagement. There are real cases where a larger, more traditional firm is exactly what you need. Board reports, audit committees, and certain regulatory contexts care about who signed the cover page. A Big 4 logo is a feature, not a bug. FM doesn't compete on logo recognition. Pharma compliance, defense contracting, certain financial services, and similar domains require deep regulatory expertise that takes years to build. FM specializes in mid-sized AI and software work, not regulated industry compliance. Big consultancies can put 30 people on a project next Monday and stand them down a month later. FM is small by design and can't match that flex. If your engagement model assumes a large rotating bench, FM is the wrong shape. Some procurement processes specifically require certain firm characteristics — minimum revenue, partner-track structure, named consortium membership, particular RFP boilerplate. FM is structured very differently and doesn't try to fit those forms. ## When FM is the better fit The mirror image. FM is built for engagements where: - You want **working software**, not a deck. - You want **senior people doing the work**, not a layered team. - You want to **own everything** that gets built — code, data, and roadmap. - You want **outcomes-based pricing** so the timeline isn't an incentive to expand scope. - You want to **ship in weeks, not quarters.** - You want a partner who is **honest about the scope** they're not the right fit for. If most of those resonate, the conversation usually gets short and useful. ## FAQ ### Isn't "traditional consultancy" a strawman? Sometimes. The traditional consulting model still does some things genuinely well — the comparison above isn't meant to say one is universally better. It's meant to say they're optimized for different problems. The honest framing is that FM is built around modern delivery assumptions that big firms can't easily adopt without restructuring, and big firms have institutional capacity that FM doesn't try to replicate. ### Does FM ever recommend a traditional consultancy to a prospect? Yes. If the engagement clearly fits the criteria in "When a traditional consultancy is the better fit," FM says so during the scoping call. There's no upside to taking work FM isn't the right shape for. ### How does FM stay current without a traditional firm's R&D budget? FM runs on the same kind of systems we build for clients. The team uses Claude, Claude Code, and modern agent frameworks every day in the actual work — that's the "R&D." Staying current is operationally cheaper when the tools you sell are the tools you use internally. ### Can FM scale up if our engagement grows? Yes. FM maintains relationships with a network of vetted development partners — senior practitioners and specialist boutiques — that get brought in when an engagement needs more capacity than the core team. These are not offshore junior contractors or staff-augmentation services; they're independent senior operators held to the same bar as FM’s own team. If an engagement legitimately requires a large rotating bench at body-shop pricing, FM will say so upfront and point you to a firm that fits. ### Is FM's pricing actually cheaper than a traditional consultancy? Sometimes meaningfully cheaper, sometimes not. The unit economics are different: FM's per-week rate is high because the team is senior-only, but engagements are shorter and outcomes-based, so total spend often lands lower. The bigger win is usually time-to-value, not headline price. --- Looking for an AI consultancy that delivers working systems, where senior people do the work, and you own everything that gets shipped — or trying to figure out whether a traditional firm is actually the right fit instead? [Get in touch](/get-started). FM’s answer in 30 minutes is sometimes "we’re not the right fit, here’s who is." --- ## https://www.buildfm.com/resource-center/custom-software-vs-saas # When Should a Growing Business Choose Custom Software Over SaaS Solutions? Your company is growing—and you've hit that inevitable inflection point where your current software is becoming a constraint instead of an enabler. Maybe you're pushing your CRM way beyond what it was designed to do. Or you're using spreadsheets to bridge gaps between systems that don't talk to each other. Or your team spends hours every week working around platform limitations instead of working. The question becomes: do you find another SaaS platform, or do you build custom? Ten years ago, the answer was almost always "find a better SaaS tool." Custom development was expensive, slow, and risky—reserved for enterprises with big budgets and bigger IT departments. Today? That calculation has changed dramatically. ## The SaaS Sweet Spot and When You've Outgrown It SaaS platforms are brilliant for certain stages and use cases. They get you operational fast, handle infrastructure complexity you don't want to manage, and solve common problems that don't require customization. When you're starting out, SaaS is usually the right call. Why build email marketing software when Mailchimp exists? Why create project management tools when dozens of good options are available? But as you grow, your business becomes less "common" and more unique. The workflows that gave you competitive advantage don't fit into SaaS templates. The processes you've refined over years of optimization can't be replicated in platforms designed for the generic use case. The integration between systems becomes a tangled mess of Zapier workflows and CSV exports. You've outgrown SaaS when: **Your team spends significant time working around platform limitations** If your people are using spreadsheets alongside expensive software because the platform can't handle your workflow, that's a red flag. You're paying for software but still doing manual work. Example: A client was using a popular project management platform but couldn't track their specific approval workflow. They maintained a separate spreadsheet to track which projects were at which approval stage, manually updating both systems. Eight to ten hours weekly on reconciliation work. **Feature requests consistently get "that's not on our roadmap" responses** SaaS vendors build for the broadest possible market. Your specific needs aren't their priority unless thousands of other customers want the same thing. When every feature you need is "coming in a future release" or not coming at all, you're trying to fit your business into someone else's vision. **Integration costs and complexity are escalating** At first, connecting your tools together seems manageable. Then you're maintaining 15 Zapier workflows, writing custom scripts to move data between systems, and still having data sync issues. A financial services client was spending $4,500 monthly on integration platforms plus another 20 hours weekly of staff time troubleshooting data inconsistencies. They rebuilt that workflow with custom software. Total integration cost dropped to near-zero because everything ran in one system. **Your subscription costs are scaling faster than your value** Many SaaS platforms have per-user or per-transaction pricing that works fine initially but becomes punitive as you scale. Example: A logistics company was paying $18,000 monthly for a platform charged per shipment. Their volume was growing 30% annually, meaning software costs would hit $270,000 annually—for software they were only using about 40% of its features. Custom solution cost them $85,000 to build and $12,000 annually to maintain. ROI in year one. **You're delaying market opportunities because your platform can't support them** When you can't enter new markets, launch new services, or serve new customer segments because your software doesn't support it, you're not just wasting money on tools—you're missing revenue opportunities. An education company wanted to expand internationally but their SaaS platform didn't support multiple currencies or language localization. They could either delay expansion indefinitely or build custom. They built custom. Revenue increased 40% in the first year from international markets they couldn't have served otherwise. ## The Economics Have Changed Custom software development is dramatically cheaper and faster than it used to be. AI-powered development tools let experienced engineers build in weeks what used to take months. Modern development frameworks provide pre-built components for common functionality (authentication, payments, notifications) that used to require weeks of custom development. Cloud infrastructure means you're not managing servers—deployment and scaling happens automatically. The operational burden that made custom software expensive to maintain has largely disappeared. A custom application that would have cost $250,000 and taken 9 months in 2015 might now cost $80,000 and take 10-12 weeks. That changes the ROI calculation completely. ## When Custom Software Makes Business Sense ### Your Business Model Depends on Proprietary Processes If your competitive advantage comes from doing things differently than competitors, your software needs to support that uniqueness—not force you into industry-standard workflows. Example: A consulting firm had developed a proprietary client assessment methodology that was central to their value proposition. No CRM platform supported their process. Custom solution let them embed their methodology directly into their software. Sales cycle shortened 30% because their system reflected how they work. ### Integration Between Systems Is Critical and Complex When you need seamless data flow between multiple business functions, custom development that treats everything as one system is often simpler and more reliable than maintaining integrations between multiple SaaS platforms. One client had 11 different SaaS tools that needed to share data. We consolidated core functions into a custom platform that reduced their tool count to 4, eliminated most integration headaches, and cost less monthly than their previous SaaS stack. ### You Need Specific Features That SaaS Vendors Won't Build SaaS vendors optimize for the broadest market. If your needs are specific to your industry niche or business model, you're probably not getting those features any time soon. A manufacturing client needed highly specific inventory allocation logic based on their just-in-time production model. Standard inventory management platforms couldn't handle it. Custom development took 8 weeks and delivered exactly what they needed. ### Your Monthly SaaS Costs Are Approaching Custom Development Costs Sometimes building custom is cheaper than continuing to pay SaaS subscriptions. If you're spending $6,000+ monthly on SaaS tools that aren't quite working ($72,000 annually), and custom development costs $80,000-$120,000, you might achieve ROI within 12-18 months while getting software that fits your needs. ## The Hybrid Approach Often Works Best This doesn't have to be all-or-nothing. Many businesses succeed with a hybrid approach: **Use SaaS for commodity functions:** Email, calendar, documents, communication—use standard tools. No need to reinvent these. **Build custom for core differentiation:** The software that runs your unique business processes, your competitive advantage, your strategic operations—build this custom. **Integrate selectively:** Connect your custom core with SaaS tools around the edges where it makes sense. Example: A client built custom software for their core service delivery workflow (their unique value proposition) but used off-the-shelf tools for HR, accounting, and email. Their custom core integrated with these standard tools where necessary. Result: They got the benefits of custom where it mattered while avoiding rebuilding solved problems. ## The Risk Question "Isn't custom development riskier than using established SaaS?" It was. Not anymore—if you do it right. **Old custom development:** Months of specification writing, big upfront commitment, one reveal after months of work, inflexible scope. **Modern custom development:** Working prototypes in weeks, iterative development, continuous feedback, adjust as you learn. The risk profile has inverted. SaaS risk is now multi-year commitment to platforms that might not grow with you, vendor lock-in, and compounding costs as you scale. Custom development risk—when done with modern approaches—is lower because you're learning and validating continuously rather than betting everything on spec documents. ## What About Maintenance? "We don't have the technical team to maintain custom software." Fair concern. But consider: You're already maintaining your SaaS stack—managing accounts, troubleshooting integrations, supporting users, working around limitations, evaluating new tools when current ones don't work. Modern custom software built with current frameworks requires far less maintenance than you'd expect. Most can be maintained with a few hours monthly from a capable developer, plus occasional feature enhancements. You can contract ongoing maintenance with your development partner. Many of our clients have monthly retainer arrangements where we handle updates, improvements, and support. The maintenance burden is real but manageable—and often less demanding than managing a complex SaaS stack. ## The Decision Framework Ask yourself: 1. **Are we spending more time fighting our tools than using them productively?** 2. **Are platform limitations preventing business opportunities worth more than custom development would cost?** 3. **Would owning our core software give us competitive advantage?** 4. **Are we approaching or exceeding custom development costs with annual SaaS spending?** 5. **Do we have workflows or processes that are genuinely different from standard industry practices?** If you answer "yes" to multiple questions, custom development probably makes business sense. ## The Bottom Line The decision isn't "SaaS vs. custom" as binary opposites. It's "what combination of tools gives us the best ROI and strategic advantage?" For growing mid-size businesses, that increasingly means custom development for core business processes combined with SaaS for commodity functions. The businesses winning in competitive markets recognize: software isn't just a tool anymore—it's a competitive advantage. And competitive advantage doesn't come from using the same platforms as your competitors. Ten years ago, custom software was a luxury. Today, it's becoming table stakes for companies that want to compete on more than just price. --- ## https://www.buildfm.com/resource-center/automation-without-job-elimination # Can Automation Reduce Operational Costs Without Eliminating Jobs? "We're considering automation, but we're concerned about the impact on our team. We don't want to eliminate jobs—but we do need to control costs as we grow. Is there a path that works?" Yes. And it's more common than the "automation eliminates jobs" narrative suggests. Here's why automation typically augments teams rather than replacing them—and how that still delivers substantial cost reduction. ## The Reality Most Businesses Face: Capacity Constraints, Not Excess Labor Here's what I hear constantly from mid-size business leaders: "We're growing but can't hire fast enough to keep up." "My team is underwater—they're working 50-60 hour weeks." "We have to turn down opportunities because we don't have capacity." "Every person we hire just creates more management burden." Most businesses aren't overstaffed—they're constrained. The problem isn't too many people; it's not enough capacity. Automation solves this by expanding what existing teams can accomplish without proportional headcount growth. ### What This Looks Like A logistics company had a 12-person operations team handling 800 shipments weekly. Business was growing 30% annually. Without automation: They'd need to hire 3-4 additional people within 12 months to handle increased volume. With automation: Automated routing, scheduling, and customer communication freed up ~35% of team capacity. The same 12 people could handle 1,080 shipments weekly. Result: 35% volume growth without new hires. **Cost reduction:** $240,000+ in avoided hiring costs (3 positions @ $80K loaded cost) No jobs eliminated. Cost reduction achieved through avoided hiring as the business scaled. ## Automation Redirects People to Higher-Value Work Your data analyst didn't become an analyst to spend 15 hours weekly copying data between spreadsheets. Your customer service team didn't sign up to answer the same 10 questions 50 times daily. Automation that eliminates tedious work frees people to do the work they were hired for. **Before automation:** Customer service team: 60% answering routine FAQs, 40% handling complex issues requiring human judgment **After automation:** Automated system handles routine FAQs; Customer service team: 5% overseeing automation, 95% handling complex issues requiring human expertise Same team size. Dramatically different value delivered. A financial services client automated tier-1 customer inquiries. Their support team went from handling 450 total inquiries weekly (mix of simple and complex) to automation handling 280 simple inquiries while humans handled 170 complex inquiries plus 30 automated escalations. Impact: - Customer satisfaction improved (simple questions answered instantly, complex issues got more attention) - Team morale improved (less monotonous work) - Capacity freed up to launch proactive outreach program (generated upsell revenue) Cost reduction came from what the team could accomplish, not from reducing the team. ## Avoided Hiring Is Real Cost Reduction "But if we're not eliminating positions, how are we reducing costs?" Avoided hiring is real money saved. If your growth trajectory requires hiring 5 additional people over the next 18 months at $75K average loaded cost, that's $375,000 annual run-rate increase. Automation that allows handling that growth with existing team saves $375,000—without eliminating a single current job. This is particularly valuable for businesses facing: **Tight labor markets:** When hiring is difficult, automation solves capacity problems without competing for scarce talent. **Recruiting costs:** Finding, hiring, and training new employees is expensive. Avoiding that cost is real savings. **Management span of control:** Every new hire adds management burden. Smaller teams are often more efficient and easier to manage. **Real estate and overhead:** More people require more space, equipment, and support. Automated capacity doesn't. ## Automation Makes Existing Teams More Effective Instead of replacing people, automation amplifies their capabilities. ### Data Analysis Example **Before automation:** - Analyst spends 20 hours weekly gathering and cleaning data - 10 hours weekly on analysis - Capacity: 2-3 substantial analyses monthly **With automation:** - Automated data gathering and cleaning - Analyst spends 25 hours weekly on analysis - Capacity: 6-8 substantial analyses monthly Productivity increase: 3× more output from same person. Cost reduction mechanism: You can support 3× more data-driven decisions without hiring 3× more analysts. ## The Retention Value of Eliminating Soul-Crushing Work People hate tedious, repetitive work. Automation that eliminates it improves retention. High turnover is expensive: recruiting costs, training time for replacements, lost productivity during transitions, and institutional knowledge loss. A client had 35% annual turnover in their data entry team. They automated most data entry, redeploying team members to more interesting data quality and analysis work. Turnover dropped to 12% annually. For a 15-person team at $50K average loaded cost: - Previous turnover: 5.25 people annually @ ~$50K replacement cost each = $262,500 - New turnover: 1.8 people annually = $90,000 - **Annual retention savings: $172,500** No positions eliminated. Significant cost reduction through improved retention. ## Scaling Without Linear Headcount Growth The most powerful cost reduction comes from breaking the linear relationship between volume and headcount. ### Old Model: Linear Scaling Volume up 40% → Headcount up 35-40% Your operations cost structure scales almost linearly with growth. Profit margins stay constant or decline due to management overhead of larger teams. ### New Model: Exponential Scaling Volume up 40% → Headcount up 10-15% Automated capacity handles bulk of volume growth. Humans focus on work requiring judgment. Profit margins expand with scale. Example comparison: **Company A (no automation):** - Current: $10M revenue, 50 employees, 20% net margin - In 3 years: $16M revenue, 80 employees, 18% net margin (management overhead increased) **Company B (strategic automation):** - Current: $10M revenue, 50 employees, 20% net margin - In 3 years: $16M revenue, 60 employees, 28% net margin Both grew 60%. Company A added 30 employees and saw margins compress. Company B added 10 employees and saw margins expand by 40%. ## Automation Enables Capabilities That Weren't Feasible Manually Sometimes automation's value isn't replacing existing work—it's enabling work that wasn't possible before. **24/7 operations:** Automation can monitor systems, respond to inquiries, process transactions around the clock. Staffing this with humans would be prohibitively expensive. **Personalization at scale:** Manually personalizing communications for 10,000 customers isn't feasible. Automated personalization is. **Real-time processing:** Humans can't process information in milliseconds. Automation can—enabling real-time responses that delight customers. These capabilities generate revenue or competitive advantages that wouldn't exist without automation—value creation, not cost reduction through job elimination. ## The Strategic Conversation With Your Team How you introduce automation to your team matters enormously. **Wrong approach:** "We're implementing automation to reduce headcount costs." Creates fear, resistance, and potentially your best people leaving preemptively. **Right approach:** "We're implementing automation to eliminate the tedious work that frustrates everyone, so you can focus on interesting work that requires your expertise. This lets us grow without overwhelming the team." Creates excitement and buy-in. Be honest: automation might mean different roles for some people. The data entry specialist might become a data quality analyst. That's not job elimination—it's role evolution. With proper training and support, most people welcome moving to more interesting work. ## The Real Cost Reduction Math Actual numbers from a client: **Before automation:** - Operations team: 25 people @ $60K average loaded cost = $1.5M annually - Supporting: $12M revenue - Revenue per operations employee: $480K **18 months later (with automation):** - Operations team: 27 people @ $60K average = $1.62M annually - Supporting: $18M revenue - Revenue per operations employee: $667K **Results:** - Revenue increased 50% - Headcount increased 8% - Cost as % of revenue decreased from 12.5% to 9% - Absolute cost increased $120K, but that growth would have required 10-12 additional hires (~$660K) without automation **Net cost reduction:** ~$540K annually in avoided hiring costs, while still adding 2 positions to handle work automation couldn't fully replace. That's the typical pattern: modest headcount growth supporting substantial revenue growth, delivering dramatic per-employee productivity improvements. ## The Bottom Line For most growing businesses, the pattern is: 1. **Automate tedious, repetitive work** that frustrates employees and consumes capacity 2. **Redeploy people to higher-value work** requiring human judgment and expertise 3. **Handle growth with existing teams** rather than proportional hiring 4. **Achieve cost reduction through avoided hiring** as business scales The result: - No jobs eliminated (often modest growth in interesting roles) - Improved employee satisfaction (less tedious work) - Substantial cost reduction (avoided hiring + efficiency gains) - Better customer experience (faster, more accurate service) - Higher per-employee productivity and profitability The businesses succeeding long-term recognize: people are your most valuable, expensive resource. Automation should maximize their impact on revenue-generating and strategic activities, not replace them entirely. The question isn't "how many jobs can we eliminate through automation?" It's "how can we use automation to make our team dramatically more effective while creating better work experiences?" Answer that question well, and cost reduction follows naturally—without the organizational trauma of layoffs or the talent loss from people preemptively leaving. --- ## https://www.buildfm.com/resource-center/automation-vs-intelligent-automation # What's the Difference Between Automation and Intelligent Automation? A marketing director recently told me she "automated" their email campaign process. When I asked how, she explained they'd set up scheduled sends in their email platform. That's not automation—that's a scheduled task. Then she showed me their new intelligent automation system that analyzes email engagement, segments audiences based on behavior, adjusts send times per recipient, and personalizes content based on past interactions. All without human intervention. *That's* intelligent automation. The difference matters because you'll invest very differently depending on which type your processes actually need. ## Traditional Automation: Follow the Rules Exactly Traditional automation is basically: "If this happens, do that." It follows rigid, predetermined logic: - Every Monday at 9am, generate and send the sales report - When a form is submitted, copy the data to this spreadsheet and send a confirmation email - If inventory drops below 100 units, send a reorder alert - When an invoice is approved, process payment and update accounting records This works great for processes that are: - Highly structured and consistent - Follow clear, simple rules - Have predictable inputs and outputs - Don't require judgment or interpretation Traditional automation has been around for decades. It's reliable, cost-effective, and perfect for tasks like scheduled backups, data transfers between systems, batch processing, and rule-based workflows. The limitation? It completely breaks when it encounters something outside its programmed rules. ## Intelligent Automation: Make Decisions Based on Context Intelligent automation incorporates AI to handle variability, understand context, make judgments, and adapt to changing conditions. Instead of rigid rules, intelligent automation can: - Process unstructured data (emails, documents, images, voice) - Understand intent and context - Make decisions within defined parameters - Learn from patterns and improve over time - Handle exceptions and edge cases - Adapt to changing conditions Let me show you the difference with a real example. **Customer inquiry routing:** **Traditional automation** might look for keywords: if the email contains "refund," route it to the returns department. Simple, fast, works most of the time. But what if the email says: "I received my order yesterday and I'm absolutely thrilled—this product is amazing! My only question is whether I can get a refund on the shipping charges since it arrived two days earlier than expected?" Traditional automation sees "refund" and routes it to returns. Wrong department entirely—this is actually a compliment with a simple billing question. **Intelligent automation** reads the entire email, understands it's a positive message with a minor question, analyzes the customer's history (first-time buyer? long-term customer?), assesses urgency and sentiment, and routes it to the appropriate team (probably billing, with notes about the positive feedback) with appropriate priority. That's the difference. Traditional automation follows rules. Intelligent automation understands context. ## When Traditional Automation Is Enough Intelligent automation isn't always better. It's more expensive, more complex to implement, and sometimes overkill. Use traditional automation when: **The process is genuinely rule-based and consistent** If 99% of cases follow the same simple logic, traditional automation is faster, cheaper, and more reliable. Example: When a new customer signs up, create their account, send a welcome email, and add them to the CRM. No interpretation needed—just execute the steps. **Speed and reliability are more important than flexibility** Traditional automation is faster and more predictable. If you need guaranteed performance within milliseconds, traditional automation beats intelligent automation. Example: Payment processing. You don't want AI "interpreting" whether to charge a credit card. You want reliable, fast execution of clearly defined steps. **The cost-benefit doesn't justify intelligence** Intelligent automation costs more to implement and maintain. For simple, low-volume tasks, traditional automation delivers better ROI. Example: If you're processing 20 expense reports monthly, traditional automation (route to manager for approval, then to finance for processing) is fine. You don't need AI interpretation. **Debugging and transparency are critical** Traditional automation is straightforward to debug. When something fails, you can see exactly which rule caused the failure and why. Intelligent automation can be more opaque in its decision-making. ## When You Need Intelligent Automation Intelligent automation becomes valuable when processes have inherent variability, ambiguity, or complexity. **Processing unstructured data** Emails, documents, images, voice calls—anything that doesn't come in a neat, structured format. Example: Processing vendor invoices that come in dozens of different formats. Traditional automation breaks because each vendor's invoice is different. Intelligent automation extracts the relevant information regardless of format. **Handling exceptions and edge cases** Real-world processes rarely follow simple rules 100% of the time. Intelligent automation handles the 10-20% of cases that don't fit standard patterns. Example: Customer support inquiries. Most follow patterns, but there's huge variation in how people describe problems. Intelligent automation can understand "my thing won't turn on" and "device fails to initialize" as describing the same issue. **Making judgment calls within defined parameters** When decisions require weighing multiple factors or understanding context rather than following simple if-then logic. Example: Prioritizing support tickets based on customer value, urgency, complexity, and current system load—not just "first in, first out." **Processes that benefit from continuous learning** Intelligent automation can identify patterns humans miss and improve over time. Example: Fraud detection. Patterns evolve constantly. Intelligent automation adapts to new fraud tactics by learning from patterns across thousands of transactions. ## The Hybrid Approach: Most Effective Solutions Use Both The best solutions combine traditional automation and intelligent automation strategically. **Use intelligent automation for flexible front-end processing** Let AI handle the variable, unstructured inputs—reading emails, classifying documents, understanding requests. **Use traditional automation for reliable back-end execution** Once intelligent automation has interpreted and classified the work, traditional automation can execute the structured workflow reliably and fast. **Real example: Customer onboarding** **Intelligent automation handles:** - Reading and extracting information from contracts (which come in various formats) - Understanding customer requests during onboarding calls - Identifying which onboarding template fits each customer's needs - Detecting issues or special requirements that need human attention **Traditional automation handles:** - Creating accounts with extracted information - Provisioning access and resources - Sending templated communications - Updating CRM with structured data - Triggering billing workflows This hybrid approach delivers both flexibility (handling variation) and reliability (executing structured tasks consistently). ## The Cost Question **Traditional automation:** Lower implementation cost, minimal ongoing costs. ROI is usually straightforward because it's mostly about time savings on well-defined tasks. **Intelligent automation:** Higher implementation cost, ongoing costs for AI platforms or APIs, more complex to maintain. ROI comes from handling tasks that would otherwise require human judgment or dealing with volume that couldn't be processed manually. For mid-size businesses, the question is: which automation type delivers better ROI for each specific process? A financial services client asked us to automate document processing. We analyzed their documents: - 60% were standardized forms that looked identical every time - 40% were custom documents from clients in various formats Our solution: - Traditional automation for the standardized forms (fast, cheap, perfect accuracy) - Intelligent automation for custom documents (handles format variability) Cost was 30% less than using intelligent automation for everything, with better performance on the structured documents. ## How to Decide What You Need Ask these questions about each process you want to automate: **Is the input consistent and structured?** Yes → Traditional automation probably works No → You likely need intelligent automation **Does the process require interpretation or judgment?** Yes → Intelligent automation No → Traditional automation **Are there frequent exceptions or edge cases?** Many → Intelligent automation Few → Traditional automation **What's the volume?** High volume with low variability → Traditional automation High volume with high variability → Intelligent automation Low volume → Probably traditional automation (cost-effectiveness) **What happens when automation fails?** Critical failure → Traditional automation (more predictable) Tolerable failure → Intelligent automation can work ## The Bottom Line Don't get sold on "AI automation" for everything. Sometimes you need intelligence, sometimes you need simple rule execution, and often you need both. The companies getting automation right match the automation approach to the process requirements—using intelligent automation where variability and complexity justify the investment, and traditional automation where reliability and simplicity deliver better ROI. Start by mapping your processes. Identify which parts require interpretation and judgment (candidates for intelligent automation) and which parts are structured execution (candidates for traditional automation). Then implement strategically, measuring ROI honestly, and expanding what actually works. The goal isn't to use the most sophisticated automation possible. The goal is to automate effectively in ways that deliver measurable business value. --- ## https://www.buildfm.com/resource-center/announcing-virtuosos-community # Announcing the Virtuosos Community ## Virtuosos: A New Community for Agentic Product Development At FM, we've been helping companies navigate the AI revolution in digital product development. Today, we're excited to announce something new: **[Virtuosos](https://virtuosos.dev)**, a community for product managers, UX designers, design professionals, and engineers who are ready to pioneer the future of how digital products are built. The way we create digital products is fundamentally changing. AI isn't just another tool—it's becoming an active collaborator in every stage of product development. We've seen this transformation firsthand through our work with clients, and we believe the most exciting innovations will come from practitioners who embrace this shift early. That's why we're launching Virtuosos: to bring together the builders, thinkers, and experimenters who aren't waiting for the future to arrive—they're creating it. ## What is Agentic Product Development? Agentic product development represents a new paradigm where AI agents become active collaborators in the product creation process. It's about augmenting human creativity and judgment to build products that were previously impossible. In this new world: - **Product Managers** leverage AI to analyze vast amounts of user data, predict market trends, and generate product strategies at unprecedented speed - **UX Designers** collaborate with AI to rapidly prototype, test, and iterate on designs, creating more personalized and accessible user experiences - **Engineers** work alongside AI agents that can write, review, and optimize code, allowing them to focus on architecture and innovation - **Design Professionals** use AI as a creative partner, exploring design spaces and generating solutions that push beyond conventional boundaries ## What Virtuosos Offers As we build this community from the ground up, we're starting with the essentials and growing based on what our members need: - **Community Forums**: A space for discussions on agentic workflows, AI tool integration, and emerging patterns in product development - **Learning Opportunities**: We're developing both free resources and training programs to help members level up their AI collaboration skills - **Regular Updates**: A newsletter sharing insights, member experiences, and practical tips for implementing AI in your workflow - **Atlanta Meetups**: Starting with informal gatherings in our home base, with plans to expand as the community grows ## Building From Atlanta, Thinking Globally While Virtuosos welcomes members from anywhere in the world, we're proudly rooted in Atlanta. We believe in the power of in-person connection and are committed to hosting regular gatherings where members can collaborate, experiment, and build relationships beyond the digital realm. These meetups will evolve from casual conversations to workshops and hackathons as our community grows, always focused on hands-on exploration of what's possible when humans and AI work together. ## Join Us in Shaping the Future Virtuosos is for anyone who believes that the future of digital product development lies in human-AI collaboration. Whether you're a product manager curious about AI-driven user research, a UX designer experimenting with generative interfaces, or an engineer building autonomous systems, we want you to be part of this journey. We're not looking for experts—we're looking for explorers. People who are asking questions like: - How can AI help us understand users in deeper ways? - What new design patterns emerge when AI is a collaborator? - How do we build products that learn and adapt? - What does responsible AI implementation look like in practice? ## Get Involved Ready to join a community that's inventing the future of product development? Visit [virtuosos.dev](https://virtuosos.dev) to sign up and connect with fellow pioneers. As we grow Virtuosos, we'll be guided by our members' needs and interests. This is your chance to help shape a community from its earliest days and be part of something transformative. At FM, we've always believed in pushing boundaries and exploring what's next. With Virtuosos, we're creating a space for everyone who shares that vision to come together and build the future. --- ## https://www.buildfm.com/resource-center/ai-empowered-development-difference # What Makes AI-Empowered Development Different from Traditional Software Development? You've probably heard about AI-powered development tools. Maybe you've seen developers using Claude Code or GitHub Copilot and wondered if it's substantial or superficial. Here's the truth: AI has fundamentally changed how software gets built, and if you're not leveraging it, you're competing at a significant disadvantage. ## The Reality of AI-Assisted Development Let's clear up a common misconception. AI-empowered development doesn't mean you type a prompt and out pops a finished application. That's not how this works. Experienced engineers use AI tools to handle the tedious, repetitive parts of coding that used to consume their time. Before power tools, carpenters spent hours hand-sawing lumber. Power tools didn't make carpentry skills obsolete—they freed skilled craftspeople to focus on design, joinery, and finishing work that requires genuine expertise. AI tools generate boilerplate code, suggest optimizations, catch common errors in real-time, write tests, and create documentation. They're handling the equivalent of "hand-sawing lumber" while your developers focus on architecture, business logic, and solving the unique challenges that actually matter for your business. ## The Speed Difference Is Real and Dramatic Projects that traditionally took months now take weeks. Features that required entire teams can be built by smaller, focused groups. I recently watched a team build a customer portal in six weeks that would have taken four months using traditional approaches. Not because the developers worked longer hours—because AI tools accelerated every step of the process. When a developer needs to implement user authentication, they don't spend three days researching best practices and writing code from scratch. AI tools suggest secure, modern implementations in seconds. The developer reviews it, ensures it fits their architecture, and moves on. That three-day task just became a three-hour task. Multiply that efficiency gain across every component of your application, and you understand why timelines have compressed so dramatically. ## The Developer's Role Becomes More Important, Not Less Here's a counterintuitive truth: AI-empowered development actually requires more senior, experienced developers. Why? Because someone needs to evaluate what AI suggests, ensure architectural coherence, maintain code quality, and make the critical decisions that determine whether your software scales or becomes a maintenance nightmare in two years. AI is exceptionally good at pattern matching and generating code based on common solutions. It's not good at understanding your unique business constraints, evaluating tradeoffs, or architecting systems that need to evolve over five years. Think of AI as a powerful accelerator that amplifies the capability of skilled engineers. Junior developers using AI might build something that looks functional but has fundamental architectural problems. Senior engineers using AI build better software, faster, because they're leveraging AI's strengths while applying their judgment to the decisions that actually matter. ## For Your Business, This Means Velocity The real competitive advantage isn't cost reduction—it's velocity. While your competitors spend three months planning and building a feature, you can build, test, get user feedback, and iterate twice. You can test more ideas, validate more assumptions, and respond to market changes faster. One of our clients wanted to explore whether their customers would use a mobile app. With traditional development, they'd need to commit significant budget and time before learning if customers even wanted it. With AI-empowered development, we built a functional prototype in three weeks. Customers loved the concept but wanted different features than originally planned. We adjusted course immediately—before investing in the wrong solution. That's the power of velocity. You're building faster, learning faster, and adapting faster. ## The Quality Question I know what you're thinking: "Faster development usually means lower quality." You're right to be skeptical—that's been true historically. But AI-empowered development actually improves quality when done correctly. AI tools catch common errors in real-time, suggest security improvements, identify potential bugs before they reach production, and ensure consistent coding standards across your codebase. The caveat is "when done correctly." This requires experienced developers who know what good looks like and can evaluate AI suggestions critically. It requires code reviews, testing, and quality standards. What it doesn't require is developers spending hours debugging syntax errors or searching Stack Overflow for solutions to common problems. AI handles that, freeing developers to focus on the complex logic where bugs actually hide. ## This Is Already Separating Winners from Losers This technology is available to everyone right now. Your competitors can use the same AI tools you can. The advantage goes to whoever adopts them most effectively first. I've seen this movie before. When cloud computing emerged, early adopters gained massive advantages—faster deployment, better scalability, lower costs. Companies that waited found themselves playing catch-up for years, trying to compete against competitors who had already optimized around cloud-native architectures. AI-empowered development is following the same pattern. Early adopters are already delivering software twice as fast as traditional shops. They're testing more ideas, shipping more features, and responding to market changes while traditional development shops are still in planning meetings. ## What This Means for Your Next Project If you're evaluating development partners or planning a software project, here are the questions you should ask: **What AI tools does your team actually use?** Not "are you excited about AI" but specifically which tools they've integrated into their workflow and how they use them. **How has your development timeline changed?** Teams effectively using AI should demonstrate materially faster delivery than traditional approaches. If they can't point to concrete examples, they're probably not leveraging these tools effectively. **What role does AI play in your development process?** You want to hear that AI accelerates routine tasks while experienced developers handle architecture and complex problem-solving. If they're telling you AI writes all their code, run. **Can you show me something you built recently?** Ask for realistic timelines. A custom application that would have taken six months traditionally should now take 8-12 weeks. If the timeline is the same as traditional development, they're not using these tools effectively. ## The Bottom Line AI-empowered development isn't future technology—it's how software gets built today. The businesses winning right now are treating software development as a competitive advantage, not a cost center. They're using AI-powered development to test more ideas, ship faster, and continuously improve while competitors are doing things the old way. Your software doesn't just support your business—in most industries now, it is your business. The velocity, quality, and innovation advantages of AI-empowered development aren't optional extras. They're table stakes for competing effectively. Which approach are you taking? --- ## https://www.buildfm.com/resource-center/fm-virtuoso-series-no2 # Virtuoso Series: No. 2 - A Conversation with R Land Join FM as we host our second Virtuoso Series event with [R Land](https://www.rlandart.com/), a local Atlanta artist with a 30 year history of creating art and loving Atlanta. FM Principal and Co-founder Brian Fletcher will host a conversation focused on: - ​Artistry and human virtuosity - The intersection of art and commerce - AI's impact on creativity - R Land's deep love of Atlanta ### Event and RSVP Information This event is a part of [Atlanta Tech Week](https://www.atl.tech/) and will take place on **June 12th, 2025** from 5:30 PM to 8:00 PM at the The Interlock building in West Side Atlanta. Get tickets for this event [here](https://lu.ma/sxo5ep0k). ### About FM's Virtuoso Series FM, a Software Consultancy born in the age of AI, is celebrating human virtuosity with a series of events that gather masters in their fields for conversations about human potential. In a time of unprecedented technological change, these masters demonstrate why human creative excellence becomes exponentially more valuable—not less. ### More About R Land North Florida native and Atlanta original, R.Land, has been filling streets, spaces and imaginations for nearly three decades. Once described by an art critic as having "the approach of Keith Haring, the enthusiasm of Disney and the vision of Finster", he ultimately defies categorization and garners a multi-generational fan base, with collectors and devotees as unique and varied as his unconventional style. Land shows large format paintings and screen-print collections all over the country, in galleries and alternative spaces alike. His “anonymous” street projects, public installations and commissioned murals continue to pop up coast to coast and the ubiquitous ‘Loss Cat’ has been carried by international retail chain Urban Outfitters and featured in the bestselling ‘Found’ coffee table book. His work appears in countless motion pictures and television series including ‘The Change Up’, ‘Aqua Teen Hunger Force’, and 'The Walking Dead' and his stylized illustrations can be seen in a variety of national publications and a score of other media. Much of Land's inspiration comes from community and he focuses on projects that work in conjunction with the efforts of organizations ranging from natural heritage and historical preservation to children’s education and just about anything involving city pride and stewardship. His art, including the iconic Pray for ATL, is now featured in the Atlanta History Center and the Georgia State Capital. *At FM, we specialize in helping mid-size businesses implement AI automation that delivers immediate ROI while building toward long-term competitive advantage. [Get in touch](/get-started) to learn how we can help your business compete and win in the AI era.* --- ## https://www.buildfm.com/resource-center/ai-automation-advantage # AI Automation ROI: How Mid-Size Companies Save 40%+ ## AI Automation: The Mid-Size Business Advantage In the race to adopt AI, mid-size businesses often feel caught between two extremes. On one side are enterprise giants with seemingly unlimited budgets deploying sophisticated AI systems. On the other are nimble startups built from the ground up around AI capabilities. Where does that leave established mid-size companies with real constraints but genuine ambitions? Surprisingly, right in the sweet spot. ## The Mid-Size AI Advantage: Just Right for Transformation Mid-size businesses possess a unique combination of attributes that make them perfectly positioned to benefit from AI automation: **Established processes, but not set in stone.** Unlike enterprises with decades of calcified procedures requiring massive change management efforts, your processes are defined enough to know what needs improvement, yet flexible enough to adapt. **Real data, but manageable volumes.** You have accumulated enough operational data to train AI effectively, but not so much that you're drowning in complex data infrastructure challenges. **Defined pain points, but room to innovate.** You know exactly where inefficiencies cost you money, yet have the flexibility to implement novel solutions without bureaucratic roadblocks. This "Goldilocks zone" creates the perfect conditions for AI automation to deliver outsized returns on your investment. ## The Six-Figure Problem: Where AI Creates Disproportionate Value For mid-size businesses, certain operational inefficiencies might seem too small to address with traditional automation. We call these "six-figure problems"-issues that waste hundreds of thousands of dollars annually but have historically been too expensive to solve with custom software. Consider these common scenarios: * The manual reconciliation process that requires two full-time employees * The customer onboarding workflow that creates a 30% drop-off rate * The inventory forecasting system that consistently leads to 15% overstocking In the past, these problems weren't large enough to justify a $250K+ custom software project. You lived with the inefficiency because the math didn't work. AI automation has fundamentally changed this equation. Today, these exact problems can often be solved for $50-75K, creating immediate positive ROI and ongoing savings that compound year after year. ## The Three-Tier Approach to Mid-Size AI Implementation For mid-size businesses, we've identified three tiers of AI automation opportunity, each with increasing levels of complexity and reward: ### Tier 1: Process Automation (3-4 Month Payback) * **Document processing:** Automatically extract, classify, and route documents * **Data entry elimination:** Replace manual data input with intelligent capture * **Approval workflows:** Streamline multi-stage approvals with intelligent routing ### Tier 2: Decision Augmentation (6-8 Month Payback) * **Inventory optimization:** Predict optimal stock levels based on multiple factors * **Resource allocation:** Intelligently assign staff and resources based on real-time needs * **Pricing optimization:** Dynamically adjust pricing based on market conditions and costs ### Tier 3: Predictive Systems (12+ Month Payback) * **Customer behavior modeling:** Predict customer actions before they occur * **Maintenance forecasting:** Identify equipment likely to fail before it happens * **Market opportunity detection:** Spot emerging trends and opportunities in your sector The key is starting with Tier 1 opportunities, using the quick wins to build momentum and fund more ambitious projects. This creates a virtuous cycle of improvement and investment. ## The Implementation Roadmap: From Quick Wins to Transformation For mid-size businesses, successful AI automation follows a clear pattern: **1. Begin with a focused assessment (2-3 weeks)** * Identify 3-5 high-impact, low-complexity processes * Quantify current costs and inefficiencies * Prioritize based on ROI and implementation complexity **2. Start with a lighthouse project (6-8 weeks)** * Choose a visible process with measurable outcomes * Implement quickly with minimal disruption * Document before/after metrics rigorously **3. Expand strategically (ongoing)** * Use savings from initial projects to fund subsequent ones * Gradually move from operational to strategic implementations * Build internal capabilities alongside external expertise This measured approach yields both immediate returns and creates a foundation for ongoing innovation-without the risks of "big bang" transformations that often plague larger companies. ## Beyond Efficiency: AI as a Competitive Moat While cost reduction is the most immediate benefit of AI automation, mid-size businesses have an even more compelling opportunity: creating a competitive advantage that larger competitors cannot easily replicate. By embedding AI automation into your core operational processes, you can: * Deliver personalized service at a scale traditionally only possible for larger competitors * Respond to market changes with agility impossible for enterprise players * Make better decisions with less overhead than competitors of any size The result is a business that combines the personalized touch of a smaller company with the operational excellence of a larger one-a powerful differentiator in almost any market. ## The Window of Opportunity: Why Now Is the Crucial Moment The timing for mid-size business AI adoption couldn't be more critical. We're in a unique window where: * AI tools have matured beyond the experimental phase * Implementation costs have dropped to accessible levels * Most competitors are still in wait-and-see mode * Technical talent is increasingly available outside major tech hubs This creates a narrow but significant opportunity for forward-thinking mid-size businesses to establish a lead that will be difficult for competitors to close once established. The businesses that move now won't just improve operations-they'll fundamentally alter the competitive landscape in their favor. ## Your Next Steps: How to Begin Without Overwhelming Your Organization For mid-size business leaders looking to capitalize on AI automation, we recommend these concrete next steps: 1. **Conduct an automation opportunity audit** (internally or with expert help) 2. **Identify 2-3 processes with clear ROI potential** 3. **Start small but think strategically** about how initial projects connect to larger goals 4. **Partner with specialists** who understand both your business context and AI implementation 5. **Measure obsessively** to build confidence and internal buy-in The most successful mid-size adopters of AI automation don't try to boil the ocean. They start with focused, high-impact projects that deliver quick wins while building toward a more comprehensive vision. --- *At FM, we specialize in helping small and mid-sized businesses implement AI automation that delivers immediate ROI while building toward long-term competitive advantage. See [FM's Agents & Automations services](/solutions/agents-automations) for how we can help your business compete and win in the AI era.* --- ## https://www.buildfm.com/resource-center/your-business-your-software # Why Custom Software Beats SaaS for Growing Businesses ## The Software Revolution No One Saw Coming _"Every company is a technology company these days."_ I’ve said that phrase countless times, usually when pitching a new client. It never got the standing ovation I imagined. If I was lucky, the 25-year-old marketing manager in the back of the room might nod approvingly. But usually, it was blank stares in the front row. Most companies don’t see themselves as software builders. They didn’t anticipate needing to write code when they started decades ago over drinks at a local bar. _Software? That sounds hard. We aren’t Google._ For them, software is just a tool—a means to an end. A department needs something (resource planning, invoice generation, customer databases), so they ask IT to find a solution. It seems good enough, so they greenlight the purchase (sorry, _procurement_) and hire a consultant to configure it. _Of course, it’ll be customized for the company_—that’s what the sales rep promised on the golf course. Then another department needs something similar but doesn’t like what Accounting picked. _Phil said the rollout was a nightmare, anyway._ Before long, you have duplicate systems doing nearly the same thing at twice the cost. I once consulted for a big-box retailer that had three separate CRM systems, costing tens of millions annually. SaaS was supposed to fix this—cheaper solutions, fewer multi-year contracts. But now, companies are stuck with a tangled mix of legacy “big rock” systems and a SaaS sprawl that’s out of control. The average company now manages 117 SaaS subscriptions, many redundant or conflicting. The result? An expensive, chaotic mess with no clear way out. ## Software Development Isn’t Hard Anymore—But No One Told You A quiet revolution has been happening—and I'm not talking about AI (yet). Building software is easier than ever. Sure, there are low-code platforms like OutSystems and Webflow, but even fully custom development has been transformed. - **CI/CD pipelines** enable one-click deployments with automated rollback. - **Global CDNs** distribute assets instantly, improving speed and security. - **Frontend frameworks** like React and Vue let developers snap together interfaces like LEGO. - **Docker containers** create identical environments for development and production. - **Distributed databases** auto-replicate across regions for seamless scaling. Put simply: software is no longer the expensive, time-consuming nightmare many IT leaders believe it to be. But the big consulting firms aren’t in a hurry to correct them. And then, AI showed up and rewrote the rules. AI didn’t just disrupt software—it _supercharged_ it. Coding assistants can now generate high-quality code instantly, thanks to the abstraction layers we’ve built into modern frameworks. If developers were still writing spaghetti code from scratch, AI wouldn’t be nearly as effective. It's this combination of abstraction layers and AI-empowered development that is so powerful. Remember those 100-person development teams? AI has turned them into teams of five. Or one. (Notice I didn’t say _zero_—you still need a technology team to build software, and AI can’t replace that yet.) ## The Real AI Revolution: Your Business, Your Code The real impact of AI-powered development isn’t about cutting jobs—it’s about unlocking opportunities that weren’t viable before. _You can now build the exact software your business needs._ Instead of adapting to a clunky off-the-shelf solution, you can create software tailored to your company’s workflows and processes. That means: - **Massive efficiency gains.** No more forcing teams to adapt to rigid, generic tools. - **Competitive differentiation.** Custom software can embed your unique IP, making it impossible for competitors to copy. - **Flexibility.** Unlike vendor-controlled platforms, you control your roadmap, scaling and evolving as needed. And this isn’t just for the big players. With development faster and cheaper than ever, businesses of all sizes can benefit from custom-built software. ## Still Skeptical? Let’s Break It Down. I get it—old beliefs die hard. Let’s tackle the most common objections. **“Custom Software Is Always More Expensive.”** Not anymore. Off-the-shelf software locks you into endless licensing fees, rigid workflows, and vendor limitations. Custom software _pays for itself_ by eliminating inefficiencies, reducing costs, and creating new revenue opportunities. **“It Takes Too Long to Build.”** That was true a decade ago. Today, AI-assisted development and modern frameworks mean you can see working prototypes in _weeks_, not months or years. The fastest companies are proving this already. **“Maintenance Is a Nightmare.”** Only if you do it wrong. With proper planning, version control, and automation, maintaining custom software is easier than wrestling with bloated SaaS subscriptions and clunky enterprise solutions. ## It’s Time to Build—Or Get Left Behind Custom software isn’t just an option anymore—it’s _the_ competitive advantage. By building solutions tailored to your business, you gain efficiency, flexibility, and control over your future. The companies that win in the next decade won’t be the ones buying software. _They’ll be the ones building it._ AI has changed the game, and businesses that embrace this shift today will lead tomorrow. The only question left: Will you build? Or will you be left behind? --- ## https://www.buildfm.com/resource-center/fm-virtuoso-series # That's a Wrap...Our First Virtuoso Series ## FM Virtuoso Series Our launch event brought Virtuosos together to celebrate creativity. We hosted our first in-person event last Friday. We invited some friends, partners, musicians, visual artists, business owners, filmmakers, and textile artists to our launch event. It's the first in a series focused on Virtuosity. FM invited a panel of inspirational and award-winning humans from the Atlanta area to share what it means to be creative in a roundtable discussion. It was a great talk on the processes that high-agency creative people follow to produce outsized results. Thanks to our panel for a great discussion! ### [Kennard Garrett](https://www.linkedin.com/in/kennard-garrett-58a39412/) GRAMMY Award-winning music producer, composer, and arranger who has worked with some of the biggest artists in music. ### [Melody Miller](https://www.linkedin.com/in/missmelodymiller/) Award-winning textile creator and founder of Ruby Star Society who pioneered collaborative female-led design in the fabric industry. ### [Christopher Glass](https://www.linkedin.com/in/christopherglass/) Multi award-winning Production Designer whose work includes the forthcoming I Love Boosters, The Jungle Book, Ms. Marvel, the now infamous Batgirl, and many commercials including the Spike Jonze’s Welcome Home for Apple. ### [Steve Sparks](https://www.linkedin.com/in/barbecuesteve/) Veteran software architect from Big Nerd Ranch who helped build the Peloton Play System and other innovations, now leading architecture at Capital One. FM would also like to thank our partners [Airia - Enterprise AI Simplified](https://airia.com) for sponsoring the event, as well as [LOCAL - The Change Marketing Company](https://www.localindustries.com/) for hosting us at their beautiful space. See more photos on our [LinkedIn post](https://www.linkedin.com/posts/itisfm_testing-1-2-3-is-this-thing-on-fm-is-activity-7286815635248955392-pI5_?utm_source=share&utm_medium=member_desktop). --- ## https://www.buildfm.com/resource-center/ebikes-and-copilots # e-Bikes and Co-pilots ## Accelerating Human Potential One of the most intoxicating aspects of software development is the flow state. It’s this magical moment when the work feels effortless. You are building features, components, UI, etc., in a relaxed yet focused state for hours. You feel invincible and capable of building virtually anything. A god among mere mortals. Most of my time spent as an engineer wasn’t quite this magical. Getting stuck on a thorny architecture issue, some obscure bug that leads you to scroll Stack Overflow for hours, or that demoralizing IM to your co-worker to come help. I’d say I got into a flow state when I was a full-time engineer about 4% of the time. I’ve been using Windsurf, the AI-assisted IDE, for the last few months. I’ve experienced this flow state dozens of times. It’s fucking magical. Many people are asking me how AI is changing software development these days. The best analogy I’ve come up with so far is that it’s like riding an e-bike. I don’t own an e-bike, but many friends do, and they have all come to me with a sparkle in their eyes, talking about how amazing an e-bike is. I think, “It’s just riding a bike, how can that be life-changing?” But they all talk about the fact that with an e-bike, every hill melts away, extending your range, increasing your enjoyment, and making you want to ride it more and more. Many people I know stopped driving their cars for ANY errands around town. Opting for the e-bike so they could enjoy the wind on their face and explore their city. On a traditional bike, a steep hill can hijack your entire experience. Your thoughts narrow to the burning in your legs, the strain in your lungs, the seemingly endless climb ahead. The beautiful scenery becomes background noise to your physical struggle. But on an e-bike, that same hill becomes just another part of the adventure. With the strain reduced, you can notice the play of sunlight through the trees, plan your next turn, or simply enjoy the fresh air. This is the same feeling I get when using an AI-assisted code editor. Without AI assistance, technical challenges can consume all your mental bandwidth. You’re so focused on the syntax details, the boilerplate, and the repetitive patterns, that the larger architectural vision becomes obscured. Just as a cyclist might miss the scenery while battling a hill, a developer can lose sight of the elegant solution while wrestling with implementation details. ## The Power of Amplification This is the key to understanding both revolutions: amplification, not automation. An e-bike doesn’t ride itself; it multiplies the power of each pedal stroke. Similarly, AI assistance doesn’t program independently; it amplifies each decision you make as a developer. You’re still the one steering, thinking, and providing the essential creative force — the technology simply helps you go further with the same effort. This amplification has amazing side effects. Once you begin to realize that you have this superpower to easily tackle any hill you encounter, you start to expand your mind to take on bigger challenges. I’ll share a recent example to illustrate this point. I’m currently involved in a startup. A small team of co-founders is building an application focused on testing marketing assets using synthetic personas. I and one of the other technical co-founders are the ones building the application in collaboration with our data science and research counterparts. It is nothing short of amazing what we have been able to accomplish as a tiny team. I built the early prototype in 2 weeks in a language/framework that I had never used. Whenever I came upon a challenge, the AI was sitting there waiting to help me get over the hill. For example, I’m not the strongest data modeler. The AI was happy to help me devise a data model for this application that was straightforward and scalable. When we got done with the POC, the team decided to re-factor the entire application into Golang. That is something we never would have done before, especially with such a small team. I need to remind you that my most recent title was Global CTO. I haven’t been a day-to-day coder for over 10 years. My co-founder is a senior VP of Technology. We know how technology works but are a little rusty in day-to-day development and have found this re-entry to software development exhilarating and empowering. All of this was made possible through AI-assisted development. The technology doesn’t just make the journey easier — it expands our notion of what journeys are possible. Of course, any transformative technology faces initial skepticism. Many cyclists initially resisted e-bikes, viewing them as “cheating” or diminishing the purity of the sport. Similarly, some developers initially viewed AI assistance with skepticism, concerned it might dilute the craft of programming. But just as e-bikes have proven to enhance rather than replace the cycling experience, AI assistance is showing itself to be an amplifier of developer creativity rather than a replacement for human insight. I hear developers scoff at the quality of responses they are getting out of coding assistants. Yes, it is sometimes hit or miss, and I have certainly gone down many rabbit holes when the AI starts to paint itself in a corner. At the end of the day, it is another tool and one that I am getting better at using every single day. Perhaps most importantly, both technologies are making their respective domains more accessible without compromising their essence. e-Bikes have transformed what’s possible in urban mobility, enabling longer commutes, easier cargo transport, and making cycling accessible to more people. In the same way, AI-assisted development is expanding what’s possible in software creation. Tasks that once seemed daunting — like writing comprehensive test suites or refactoring complex codebases — become more approachable with AI amplification. As we continue to wrestle with the changing world of software development, one thing is certain to me. What is now possible has been changed drastically. I believe that we are on the cusp of a tidal wave of custom software that wasn’t possible before, changing business and user experience in profound new ways. At my company, FM, we call it “software within reach.” The future of technology isn’t about replacement but about amplification — helping us achieve more while preserving the fundamental joy and creativity of human effort. The next time you see an e-bike glide effortlessly up a hill, think about how that same principle of amplification is transforming software development. In both cases, we’re not removing the human element — we’re empowering it, one pedal stroke, one line of code at a time.