Answers to common questions about the Loop Design Partner Program.
What is the Loop Design Partner Program, and what makes it different from a beta or free trial?
An invitation-only program providing early access to Loop prior to general availability, limited to approximately 15 organizations. Unlike a beta or free trial, participants work directly with the Tempo product team in structured 1:1 sessions, and feedback flows directly into the product roadmap. It is a co-development engagement, not an open evaluation.
How were design partners selected?
Invitations are based on portfolio complexity, Jira and Tempo product usage — particularly Structure — and the organization's capacity to provide substantive product feedback. Participants were selected because their environment reflects the use cases Loop is built to address.
Who else is in the program — and how much will Tempo share about other participants?
The cohort includes approximately 15 customers and implementation partners. Tempo will not disclose participant identities without their consent. At the September 2026 launch event, design partners will be recognized as a founding cohort; the specific form of recognition is agreed with each participant in advance.
What is the overall timeline — when does access begin, how long does the program run?
Initial access begins in late June 2026. At this stage, participants access a working prototype, not the production release. The program runs through the September launch event and general availability release (late September to early October 2026).
How many seats are available, and how long is the invitation open?
The cohort is capped at approximately 15 participants. Seats are filled as organizations confirm enrollment. Accounts that do not commit before the cohort is full may be considered for the Early Access Program (EAP), which opens in late July 2026.
Who from our organization needs to be involved, and at what level?
Two roles are required: a business stakeholder (Portfolio Manager, Head of PMO, or equivalent) who can evaluate Loop against real portfolio use cases and provide substantive feedback, and a technical resource who can configure and maintain the Jira integration. Both roles must be identified before enrollment is confirmed.
What actually happens in the weekly product sessions?
Structured 1:1 working calls with Tempo's product team covering the participant's active use of Loop, feedback on recently released features, and early visibility into capabilities in development. These are not demos — participants are expected to come with specific use cases or observations from their own platform usage.
How much total time should we expect to commit per week?
Approximately two to three hours per week: one hour for the product session and one to two hours of active platform use between sessions. The first two weeks of onboarding require additional time from the technical resource.
What does Tempo define as a successful design partner engagement?
The participant has used Loop in their live portfolio environment — not a sandbox — provided candid feedback throughout the program, and is positioned to share their experience in some public form at or after the September launch event.
What happens if our team's availability changes mid-program?
Participants should notify their Tempo contact as early as possible. Reduced availability does not affect other participants but may limit the depth of the engagement and affect eligibility for the commercial offer associated with the program.
What does "technical resources available" mean in practice?
The organization must provide someone — an employee or a designated implementation partner — with administrative access to Jira who can configure the Loop integration with guidance from the Tempo product team. Developer-level skills are not required, but systems administration access is.
What systems and access does Tempo need on our side to get started?
Access to the organization's Jira environment: project hierarchy, work item structure, and relevant custom fields. If the organization uses Structure, Capacity Planner, or Timesheets, those will also be connected during onboarding. At the Design Partner stage, Jira is the only supported work system.
What does onboarding look like — who leads it and how long does it take?
Onboarding is led by Tempo's product team. Configuration typically takes one to two weeks depending on the complexity of the Jira environment. The first product session is scheduled once the integration is complete and data is verified.
Is a security or infrastructure review required before accessing the platform?
Tempo can discuss security architecture and data handling practices during enrollment. SCIM and JIT provisioning are included in the GA build. Organizations with additional compliance requirements — data residency, certifications — should raise them before enrolling, as some may not be accommodated within the Design Partner timeline.
What usage data does Tempo collect during the program, and how is it used?
Tempo collects platform usage data — feature usage and credit consumption patterns. This informs product development decisions and feeds into pricing model validation work conducted with an external pricing advisory firm. It is not used to benchmark participants against one another.
Is our portfolio data or strategic content visible to anyone at Tempo?
Portfolio data is accessible to the product team members directly supporting the engagement and any personnel required for technical troubleshooting. Access is limited to what is necessary to support the participant. Tempo does not use participant portfolio data for any other purpose.
What are the confidentiality terms — can we discuss our participation externally?
The participation agreement governs confidentiality. Participants may confirm their involvement in general terms but should not disclose specific product features, roadmap details, or pricing that have not been publicly announced. Restrictions narrow as Loop approaches its September 2026 GA announcement.
Does participation obligate us to purchase Loop?
No. Participation does not create a purchase obligation.
What does "below-market purchase option" mean — can you share specifics?
Design partners who complete the program and choose to purchase Loop will be offered pricing below the GA market rate. Specific terms are discussed directly with each participant and are not published externally.
How does the design partner experience connect to GA pricing?
Loop's GA pricing is credit-based: a seat tier plus a credit pool. Design partners receive three months of credits at no charge, which allows them to understand their usage patterns before making a purchase decision. The GA model is Phase 1 of a two-phase structure; a more refined, outcome-based model is planned for 2027.
When and how would a transition from design partner to paying customer happen?
Commercial close can occur at any point during or after the program. Most transitions are expected in the September–October 2026 window, aligned with GA. The below-market pricing offer is time-limited; the account team will communicate the specific window in advance.
What criteria did Tempo use to select design partners?
Four criteria: (1) portfolio complexity — the organization manages competing priorities across teams with real resource allocation decisions; (2) Jira usage, ideally with Structure and other Tempo Marketplace products; (3) technical readiness to configure and maintain the integration; (4) availability to commit the required time and provide direct, substantive feedback.
What's the difference between the design partner program and the Early Access Program?
Design partners access a prototype and engage in 1:1 sessions with the product team. EAP participants access the production build and participate in group sessions. In the EAP, implementation is led by Tempo's implementation services team and partners — not the product team directly. EAP onboarding begins in late July 2026.
What if we're interested but uncertain about the technical resource requirement?
The requirement is firm, but it can be met by an implementation partner rather than an internal employee. Tempo can facilitate introductions to qualified partners. The resourcing question should be resolved before enrollment — it is better to address it upfront than to encounter a gap during onboarding.