Your business shouldn’t have to outgrow its software.
A second crew, a new location or a different way of serving customers changes what you need from your tools. The Forge connects the work today and gives customers a way to help shape what comes next.
That starts with understanding the job you need to do—not asking you to write a software specification or replace everything whenever a requirement changes.
Illustrative pathway — not a live request or a delivery commitment.
- Captured
Describe the work that needs to change.
- Planned
An evaluated need becomes approved work.
- In development
Follow the updates available for your request.
- Released
Available to your company after its rollout.
Not every request becomes planned work. Status does not establish a delivery date.
Tell us what the work needs.
Describe the missing handoff, who is affected and what a better result would look like. A dispatcher might need the office to see a schedule change before a crew leaves. A restaurant manager might need a clearer stock-to-shift handoff. These are examples of needs to discuss, not promises of new features.
Eligible customers can submit a request and add context in The Forge’s Feedback area. Request detail follows account permissions; the company roadmap is currently for Owners.
Open feedback and requests in The Forge — sign-in and eligible account access required.
A request starts a conversation.
The team can ask for context, check whether an existing capability meets the need and consider demand, engineering effort, security and product fit. Similar requests can inform a reusable improvement without exposing other companies’ private information.
Explain the problem
Bring the operational context. Comments can help clarify what would make a difference.
Understand the decision
Follow the available updates. Evaluation can lead to planned work; submission alone does not.
Check your account
A released improvement must reach your company before you can rely on it.
See the status. Understand its limits.
The existing roadmap distinguishes Captured, Planned, In development and Released. Available request history helps explain what has changed. Eligible Owners can also see an industry roadmap and register interest in shared needs.
These statuses describe recorded progress, not engineering milestones or a percentage complete. A release for another company does not mean it has reached yours.
A request without an approved engineering estimate has no established delivery window. If the team provides an estimate, it may change; a committed date requires an explicit agreement.
Availability is the start of the next conversation.
Check your company’s request status and release information for availability. For a linked request, the release workflow can show an in-app notice when a rollout reaches your company. Notices depend on the enabled workflow and an identifiable requester; email or SMS delivery is not promised. Check access rather than relying on a notification alone.
When an improvement reaches your account, try it against the original work and tell the team what remains unresolved. Released means delivered, not that your business outcome has been confirmed. This page does not offer a customer-confirmation control or a live delivery tracker.
Choose what works today. Help shape what comes next.
The Forge must help with the work you already need to run. Start with the customers, jobs, teams and finances you want to connect. Bring any unmet need to your free Forge Fit Review, with a clear distinction between current capability and future consideration.
Explore the connected platform → · See the illustrative walkthrough →