Topic

Lab

The Impact Lab custom build process -- scoping, pricing, what a build engagement looks like, and how to know if a custom build is right.

Getting Started

What it is, who it's for, and what problem it solves

What does the Lab actually build?

The Lab builds custom software when no existing tool solves the specific problem at the right level of quality and ownership. The categories are SaaS platforms, intelligence layers and AI systems, directories and marketplace infrastructure, and operational tools that run inside a business.

Guide
Hunhu — how a white-label provider directory was built from agency network needs

Hunhu started with a problem Fulcrum saw repeatedly across its own networks: agencies with trusted provider relationships had no reliable infrastructure to make those relationships searchable, bookable, and revenue-generating. We built the platform we needed and opened it to others.

Guide
Pulse — how an alignment intelligence platform was built from a nonprofit reporting problem

Pulse started with a nonprofit client whose reporting infrastructure was designed for funders, not for strategic execution. The discovery process revealed a problem that existed across multiple verticals and had no good solution. Fulcrum built one.

Guide
What is Hunhu and how does it work for agency networks?

Hunhu is a white-label provider directory platform for agencies that maintain curated networks of trusted providers. Your network, your brand, your revenue. Agencies create branded directories, providers get found across every network they join, and clients book without leaving the agency's experience.

Guide
What is Pulse and how does it help teams execute strategy?

Pulse is an organizational alignment intelligence platform. It tells leaders whether the people responsible for executing the plan actually understand it, believe in it, and have what they need to act on it. Not how they feel. Not whether tasks are moving. Whether the direction has actually landed.

Guide

How It Works

The process, architecture, setup, and what to expect

How is the Lab different from hiring a dev agency or contractor?

A dev agency executes a spec. The Lab starts from the problem. The difference shows up in every decision: what to build, what not to build, what technology to use, and how to structure ownership so you are not dependent on anyone after launch.

Guide
Can you work alongside our existing development team?

Yes. Some clients have internal developers who handle maintenance but lack the capacity or architecture experience for the initial build. We scope to what's needed and hand off cleanly.

FAQ
Do we own the code when you're done?

Yes. Everything we build for you is yours. We document it, hand it over, and train your team on maintenance. If you want ongoing support, that's available, but it's not required.

FAQ
How do I know if a custom build is the right answer?

If you've tried two or more existing tools and neither addresses your specific constraint, that's a signal. If the manual process your team is running costs more in time than a build would cost to maintain, that's a signal. We'll tell you honestly in the first conversation if we think a custom build is the right move or if an existing solution would serve you better.

FAQ
What does a typical Lab engagement look like?

Most builds run 8 to 16 weeks depending on complexity. Discovery and architecture happen in the first two to three weeks. The build phase is the bulk of the engagement. We deliver in working increments so you're not waiting 16 weeks to see anything. Pricing depends on scope; we give you a fixed quote after discovery.

FAQ
What technology does the Lab build on?

The Lab builds on a deliberate stack chosen for longevity, ownership, and independence from proprietary platforms. Every build uses open-source foundations you can maintain, extend, or hand off without licensing risk.

FAQ