JAMS Software launched JAMS Incident Management on September 1, 2026, expanding beyond its core scheduler product into on-call alerting.1 The product offers a free plan for up to five users and paid tiers starting at $6/user/month, with a fourteen-day trial of all features.3458 This launch demonstrates JAMS's innovation and growth since separating from Fortra in June 2025 and operating independently.6 The technical community will evaluate this expansion based on integration with JAMS Scheduler and the value proposition for existing customers.27
OPPORTUNITYJAMS can demonstrate product innovation and growth post-separation from Fortra, reinforcing its independent market position and credibility in the DevOps/ITOps space.16
OPPORTUNITYThe free plan and trial options create low-friction entry points that could convert prospects into paying customers across the pricing tiers.38
OPPORTUNITYThe 'built for internal use first' narrative provides authentic technical credibility that resonates with developer audiences and differentiates from competitors.2
THREATIf the launch fails to gain traction, it could signal limited market appetite for JAMS's expansion beyond its core scheduler product.
Best response strategy
AMPLIFY JAMS owns this story - removing the brand from the headline collapses the announcement, making 'amplify' the appropriate response strategy.1 The technical community values products built for internal use first, making JAMS's development approach a credibility advantage worth highlighting.2 With no prior coverage patterns to build upon, this launch represents a fresh opportunity to establish JAMS's expanded market position.
Who is watching, and what each expects from the response:
customersExisting JAMS Scheduler customers want to understand how Incident Management integrates with their current investment and whether it adds value to their workflow.7
prospectsTechnical teams evaluating on-call alerting solutions want to understand JAMS Incident Management's capabilities, pricing, and trial options.3458
partnersIntegration partners and resellers need details about the new product to position it alongside JAMS Scheduler and other offerings.6
talentCurrent and potential employees want to see the company's growth trajectory and product innovation as validation of its independent direction post-Fortra separation.6
mediaTechnical and trade media want substantive details about the product's technical architecture, differentiation, and market positioning.2
Suggested response plan
T+1-3 days
Phase 1 — Capitalize on the moment
Outcome: JAMS's own channels actively showcase the new product with technical details that resonate with the developer community and existing customers.123
comms
Publish a detailed technical announcement on the JAMS blog and website highlighting how JAMS Incident Management was built for internal use first, its integration with JAMS Scheduler, and the free/trial options.238
Target developers and technical decision-makers with a blog post demonstrating real-world use cases.
Update the JAMS website product page with comprehensive feature documentation.
Create social media posts highlighting key differentiators like the free plan and no-credit-card trial.
Done when: Announcement post is live on the JAMS blog with technical details, pricing transparency, and clear calls-to-action for the free plan and trial.
“JAMS Software has launched JAMS Incident Management, expanding our platform beyond job scheduling to comprehensive on-call alerting.1 Built initially for our own teams, this new offering provides the same reliability and integration our customers expect from JAMS.2 We're offering a free plan for up to five users with no time limit and a fourteen-day trial that unlocks every feature without requiring a credit card.38 This makes it easy for teams to evaluate how JAMS Incident Management can streamline their on-call operations.” website statement
T+2-5 days
Phase 2 — Amplify through validation
Outcome: Third-party technical outlets and partners amplify the announcement with their own coverage and validation.
comms
Coordinate with technical media outlets and integration partners to secure follow-up coverage that validates JAMS Incident Management's positioning in the DevOps/ITOps market.
Pitch DevOps/ITOps-focused publications with technical angles on the product.
Provide integration partners with briefing materials and co-marketing opportunities.
Monitor and engage with social media discussions about the launch in relevant communities.
Done when: At least three technical publications beyond the initial press release publish substantive coverage or analysis of JAMS Incident Management.
T+1-2 weeks
Phase 3 — Institutionalize the gain
Outcome: The launch moment is banked into permanent assets that continue driving awareness and conversions after the news cycle ends.
comms
Create permanent reference assets including a detailed case study, sales enablement materials, and recruiting documentation that showcase JAMS's growth and innovation.2
Develop a case study highlighting how JAMS built Incident Management for internal use first.
Your brand is having a moment — claim it to amplify. Claiming is free — your response strategy & plan become collaborative, and you get the option to display your response & status updates on this page.
One short, factual update when this story develops — nothing else, from over:heard.
Email updates
By subscribing you consent to receive email updates about this story. Double opt-in: nothing is sent until you confirm from your inbox. Unsubscribe anytime — one click in every email.
Push notifications
No email needed — alerts appear on this device.
Not jamsscheduler.com? See what over:heard would flag for your brand.
Start free →
Independent media-monitoring briefing compiled by over:heard radar from public coverage. Assessments are decision support —
not statements by, or affiliation with, the brands mentioned. · Built from public sources, cited.
Every brand has a free, permanent right of reply —
editorial policy
· Powered by over:heard by wise:able
