Questions worth answering before a workflow consultation.
A few direct answers about where Foundry fits, how implementation works and what a company should expect before deciding whether to move forward.
Is Foundry custom software?
Foundry has a shared core product. Company-specific differences are handled through configuration whenever practical. True custom development can be added when there is a real need, but the goal is not to create a separate codebase for every customer.
Do we have to change our terminology?
No. Roles, statuses, fields and workflow language can be configured around the way the company already operates when practical.
What size company is Foundry for?
Foundry is especially well suited to contractors and field-based companies managing multiple active jobs, crews and office-to-field handoffs. Trade and specialty contractors are a strong fit, and many companies may fall around 10–50 employees, but operational complexity matters more than headcount or industry label by itself.
Does Foundry replace accounting or estimating software?
Not necessarily. Foundry is focused on the operating layer that connects jobs, handoffs, scheduling, tasks, crews, materials, files and accountability. If a specialized accounting, estimating or other system already performs its job well, it can remain in place rather than being replaced for the sake of consolidation.
How does implementation begin?
With a workflow consultation. We trace how work currently moves through the company, identify the important handoffs and recurring points of friction, then use that operating map to define the initial Foundry configuration.
Is consultation remote or in person?
Either. Remote consultation works well for many companies when the right people can walk through the operation clearly. In-person consultation is available when practical and can be especially useful when the physical shop, warehouse or field workflow is part of what needs to be understood.
What happens after launch?
Foundry is refined from real use. The goal is not endless customization; it is to improve the configuration when day-to-day work exposes a clear gap, unnecessary friction or a better way to preserve the operating record.
Will every customer have separate source code?
No. Foundry is intended to maintain a stable core product and handle company differences through configuration whenever possible.
Is this website showing a real customer?
No. The companies, jobs, messages and operating examples shown on this public website are fictional and are used only to illustrate Foundry workflows.
Still have a question?
Email us directly or walk through it during a workflow consultation.