Your organization owns its data.
Keep business records and branding tied to the right organization. A parent–child relationship does not automatically share access.
Your organization.
Your data.
Connected capabilities.
FORGE™ · Where Visions are FORGED™
From the first relationship to the final payment. Bring finance, people, projects, commerce, and experiences together—with the capabilities your organization actually needs.
Explore capabilities ↓The platform
Run a business, a chapter, a nonprofit, or a portfolio. FORGE combines an operating workspace with reusable modules and purpose-built applications. Start with a practical need—not a wholesale replacement of every system.
Keep business records and branding tied to the right organization. A parent–child relationship does not automatically share access.
Connect the capabilities you need: proposals, inventory, ticketing, finance, and more. Access and configuration remain explicit.
Teams work in FORGE or a connected app. Customers, members, and guests use the appropriate branded portal or experience.
New connections. Practical outcomes.
These expanding workflows show what the platform can bring together. Module access, provider connections, and organization setup determine what is enabled.
The capability library
Find a capability, open its details, and see a practical use case. “Available” describes a deployed workflow; “Beta” and “Pilot” identify narrower implementations. Current subscription types vary by user count or organization type—not module selection. Roles, readiness, and configuration still apply.
25 of 25 capabilities
A multi-company operator reviews upcoming supplier payments without mixing every company’s finances.
Scope & setupSource accounting systems remain authoritative for their payment and balance facts.
Discuss this capability ↗A nonprofit compares attendance, sponsorship, and production costs before committing to an event.
Scope & setupSaving a scenario does not automatically change actuals or commit spending.
Discuss this capability ↗A service company reviews unpaid invoices and sends the right reminder from its own organization.
Scope & setupSources and payment links vary by application and provider. On the Runway’s customer invoice flow uses its configured Stripe connection.
Discuss this capability ↗A sales organization reviews gross profit and assignments before approving its commission cycle.
Scope & setupSource data and compensation rules must be configured; this is not a payroll processor.
Discuss this capability ↗An operator compares the value of different business cards for planned vendor spend.
Scope & setupSeparate from customer Loyalty programs. Estimates depend on current provider terms and entered assumptions.
Discuss this capability ↗A property team compares locations and tests the effect of financing and operating costs.
Scope & setupResearch evidence is distinct from assumptions; models are not appraisals or guaranteed returns.
Discuss this capability ↗A chapter records a venue contact, sponsor representative, and volunteer with their different relationships intact.
Scope & setupRecords remain organization-scoped. A matching name or email does not by itself grant access.
Discuss this capability ↗An event team assigns production milestones, attaches vendor documents, and tracks what needs attention.
Scope & setupExternal calendar feeds and application links require their respective connection setup.
Discuss this capability ↗A national association, region, and local chapter share a structure while keeping access explicit.
Scope & setupTeam membership is distinct from paid subscriptions. Parent relationships do not automatically grant access across a hierarchy.
Discuss this capability ↗A rental supplier prepares an event proposal with catalog pricing and shares a branded customer view.
Scope & setupAdvanced contributor intake and proposal evaluation are still in development. Publishing is not the same as sending, reserving stock, or collecting payment.
Discuss this capability ↗An association tracks a member’s support request through resolution without losing the conversation.
Scope & setupOrganization helpdesks must be enabled. Live chat, screen-sharing, and chatbot support remain planned.
Discuss this capability ↗An equipment provider reserves 20 units for a project and tracks partial returns before closing the job.
Scope & setupReservations, custody, and transport remain separate records with deliberate links; linking a proposal does not silently reserve stock.
Discuss this capability ↗A production company connects an outbound delivery with its return pickup and final equipment check-in.
Scope & setupStock and transport status retain separate controls. Carrier services require a configured provider.
Discuss this capability ↗A club creates a merchandise catalog with sizes, colors, and multiple fulfillment suppliers.
Scope & setupLive checkout, tax settings, shipping, and providers require organization-specific validation. A catalog alone does not activate payments.
Discuss this capability ↗A service business offers appointments around staff, rooms, capacity, and turnaround time.
Scope & setupAdditional automated notifications and invoice handoffs remain in development. Connected booking apps may retain their own reservation authority.
Discuss this capability ↗A software business connects subscription status to the appropriate application access.
Scope & setupProvider setup and application-specific entitlement wiring are required; plans do not override organization permissions.
Discuss this capability ↗A club configures its program in FORGE OS and records approved points against the right customer account.
Scope & setupManaged in FORGE OS with its existing organization permissions. A customer reward catalog, automatic earning, tiers, and universal cross-app synchronization are not enabled.
Discuss this capability ↗A gala team moves a guest from GA to an available VIP seat, revokes the old QR, and checks the current ticket at the door.
Scope & setupPayments and notifications need configured providers. Manual issuance does not collect payment. Ticketing push notifications are not yet implemented.
Discuss this capability ↗A sponsorship team distributes outreach across existing relationships and records the next action after each call.
Scope & setupCard extraction requires human review. The expanded shared prospecting workflow is being developed incrementally.
Discuss this capability ↗A nonprofit prepares a post-event impact story and routes it for review before publication.
Scope & setupChannel connections and publishing approval are configured separately; this does not imply unattended posting to every network.
Discuss this capability ↗A charity coordinates sponsors and auction items, then reviews the financial result and donor communications.
Scope & setupThese are On the Runway capabilities, not duplicated FORGE modules. Tax acknowledgments require accurate organization details and review.
Discuss this capability ↗An organizer sends branded ticket updates while keeping platform notices and marketing settings separate.
Scope & setupSMS requires provider setup and consent. Marketing campaign sending and automated collection of communications usage charges are not enabled.
Discuss this capability ↗A business starts with report imports and later connects QuickBooks while keeping its operational review process.
Scope & setupQuickBooks, Stripe, Square, Microsoft, Shopify imports, Twilio, and Shippo have specific supported workflows—not universal automatic synchronization.
Discuss this capability ↗An administrator configures a new organization’s identity and access without becoming a visible member of its team.
Scope & setupRecovery scope varies by application. SecureOne linking does not yet replace every sign-in, and verification alone does not grant organization access.
Discuss this capability ↗A project team keeps the current proposal, reference photos, and delivery instructions attached to its work.
Scope & setupShared-library adoption varies by application. Existing application document workflows remain in place.
Discuss this capability ↗Availability describes the documented implementation, not a promise that every integration is enabled for every organization. Provider accounts, permissions, and production readiness are reviewed during setup.
Built for different kinds of organizations
Illustrative workflows—not customer testimonials. Choose an organization type to see a starting point and the capabilities that support it.
Connected experiences
A shared capability does not mean a shared permission. Each connection has its own scope, and each organization keeps control of its records.
Finance, planning, relationships, commerce, and execution in an organization-aware workspace.
Open FORGE OS ↗Event planning, run of show, sponsors, vendors, fundraising, portals, and event P&L—with connected FORGE capabilities.
Explore FORGE Events ↗Linked person verification and a mobile ticket experience. Organization membership and permissions are still checked separately.
Open SecureOne ↗Story planning, media, review, and publishing preparation. Connected channels require their own setup and approval.
Explore WellTold ↗Connected applications are configured individually. A universal “Sign in with SecureOne” experience is still in development; existing sign-in and account-linking flows remain in place.
No need to turn on everything at once. We’ll map your workflow, configure the right organization and providers, and verify the journey before inviting your team or customers.
An event, an invoice queue, an equipment pool, a member program, or a customer journey.
Set branding, roles, data sources, and the payment or communication providers you need.
Test the full workflow with your team. Add capabilities as the next operational need appears.
Advanced proposal evaluation and contributor intake, additional booking notification and invoice flows, universal SecureOne-first sign-in, automated loyalty tiers and earning campaigns, Qube Builder, and expanded payroll/HR/benefits capabilities are not presented here as generally available. Provider setup, taxes, and live payment activation require separate validation.
Let’s make it practical
Tell us what your organization does, where work gets stuck, and which systems you want to keep. We’ll help you find a sensible first workflow.
Plan a tailored walkthrough ↗