Questions before
the workflow review.
A few common questions about how Foundry is set up and used.
Is Foundry custom software?
Foundry has a shared core product. Company-specific differences are handled through configuration, with custom development used only when there is a real need.
Do we have to change our terminology?
No. One of the goals is to configure statuses, fields, roles and workflow language around the way the company already operates.
What size company is Foundry for?
The initial focus is specialty contractors, often around 10–50 employees, managing multiple jobs, crews and office-to-field handoffs.
Does Foundry replace every other software product?
Not necessarily. The focus is the operating layer that connects jobs, scheduling, tasks, crews, documents and accountability. Some companies may continue using specialized accounting or estimating systems.
How does implementation begin?
With a workflow review. The objective is to understand how the company operates before deciding what should be configured.
Will every customer have separate source code?
No. Foundry is intended to maintain one stable core product and handle company differences through configuration whenever practical.
Is the consultation remote or in person?
Either. Foundry can conduct the initial workflow consultation remotely, and in-person consultation is available when practical. The purpose is the same: understand how the company actually operates before configuring the system.
Is this website showing a real customer?
No. The companies, jobs and operating examples shown on this site are fictional and are used only to illustrate Foundry workflows.