Product Roadmap: Now/Next/Later

Important Context: This roadmap is organized by strategic themes rather than specific dates. Timeframes are approximate and subject to change based on user feedback, technical discoveries, and market needs.

NOW (Next ~3 months)

In progress or starting soon

Theme: Strengthen Security & Access Control

Why it matters: Enterprise customers require robust authentication and security features to meet compliance requirements, reduce risk exposure, and enable secure team access across their organizations.

Features:

• Two-factor authentication (2FA)
• Single Sign-On (SSO) integration
• Password reset improvements

Success metrics:

• 90%+ of enterprise customers adopt SSO within first month of availability
• 2FA adoption rate of 60%+ among enterprise users
• Zero security-related escalations or churn incidents
• Reduction in password reset support tickets by 40%

NEXT (Following ~3-6 months, subject to validation)

Direction is clear, timing depends on Now initiatives

Theme: Enable Team Collaboration

Why it matters: Executives and enterprise customers increasingly work in distributed teams that need seamless real-time collaboration capabilities to improve productivity and reduce communication overhead.

Features:

• Team collaboration features
• @mentions functionality for team notifications
• Real-time collaborative editing

Validation dependencies: Completion of SSO and authentication foundation required before enabling team features. User feedback from Now security features will inform collaboration permissions model and scope.

Theme: Expand Developer Platform & Integration Ecosystem

Why it matters: Enterprise customers require API access and webhooks to integrate with their existing toolchain, automate workflows, and build custom enterprise solutions.

Features:

• API v2 launch with enhanced capabilities
• Webhook support for event-driven integrations

Validation dependencies: Security and authentication framework from Now must be complete to ensure API security. Enterprise customer validation will determine priority webhook events and API endpoints.

LATER (6+ months out, priorities may shift)

Exploratory direction, subject to change

Theme: Extend Mobile & Offline Access

Why it matters: Executive users and field teams need mobile access for on-the-go productivity, though specific use cases and platform priorities require validation.

Potential features:

• Mobile app development (platform TBD)
• Offline mode exploration

What could change: User research with enterprise customers and executives will determine primary mobile use cases, platform priority (iOS vs Android), and offline functionality requirements. Timeline and scope will be refined based on validation findings and resource availability. Competing priorities from team collaboration or API platform may accelerate or delay mobile investment.

Roadmap Philosophy

Why Now/Next/Later?
Product development for enterprise customers involves inherent uncertainty around technical complexity, integration requirements, and evolving business needs. Traditional quarterly date commitments often led to scope compromises, quality issues, or stakeholder disappointment when priorities shifted. This format maintains strategic clarity and alignment with your business goals while enabling us to deliver quality features and remain responsive to market feedback.

What the timeframes mean:

• Now = Next ~3 months. High confidence in scope and delivery timing. Resources committed, work in progress or starting soon.
• Next = Following ~3-6 months, subject to validation. Clear strategic direction, but timing depends on completion of Now initiatives and validation learnings.
• Later = 6+ months out. Exploratory direction. Priorities will shift based on market validation, technical discoveries, and strategic business opportunities.

How we make decisions:

• Enterprise customer feedback and usage analytics
• Security and compliance requirements
• Technical feasibility and architectural dependencies
• Strategic business goals and revenue impact
• Competitive market dynamics

Stakeholder Talking Points

“When exactly is Next?”
“Next means 3-6 months following completion of Now initiatives. The specific timing depends on what we learn during implementation of security features, validation with enterprise customers, and technical dependencies we uncover. We’ll communicate updates proactively as Now features complete and provide visibility into Next timing.”

“Why can’t you commit to dates?”
“Date commitments in enterprise software often led to one of three outcomes: rushing features and compromising quality, cutting scope to hit deadlines, or disappointing stakeholders when technical realities required timeline adjustments. This approach lets us maintain the quality and security standards your enterprise customers require while staying responsive to their evolving needs and technical discoveries during implementation.”

“How will I know when things move from Later to Next?”
“We review the roadmap quarterly with key stakeholders and share updates on what’s been validated and promoted between buckets. You’ll receive advance notice when Later initiatives are being validated for promotion to Next, including the specific customer feedback or market data driving the decision.”

“What if a strategic customer needs a Later feature now?”
“We evaluate strategic opportunities on a case-by-case basis. If a major customer or revenue opportunity requires a Later feature earlier, we’ll assess the tradeoffs with you: What moves from Now or Next to accommodate it? What’s the revenue impact? What technical dependencies exist? These decisions are made collaboratively with business stakeholders, not unilaterally by the product team.”

“How does this affect our revenue targets?”
“Now features (security and access control) directly address the top blockers in our enterprise sales pipeline. Next features (collaboration and API) unlock expansion revenue from existing enterprise customers and enable new integration partnerships. Later features (mobile) address a growing but not yet validated segment. This sequencing maximizes revenue impact while managing delivery risk.”