OPTIMIZELY PARTNER PROGRAM
Expand Your Optimizely Services Without Expanding Your Team.
Help your customers resolve performance issues faster with Reignite's specialized performance engineering services—delivered through a co-branded partnership.
Learn about the broader partner program. Are you an Optimizely customer?
Partner benefits
The commercial case comes first: more services to sell, more reasons for a customer to stay, and fewer escalations that land on your team with nowhere to send them.
Extend Your Team
Add specialist performance engineering expertise without permanent headcount.
Grow Revenue
Expand the scope of services delivered to existing accounts through a co-branded offering.
Improve Retention
Reduce unresolved performance incidents and protect customer relationships.
Capability extension
Give your customers access to specialist performance engineering for the engagements that need it, without hiring a discipline you do not staff full-time.
Recurring service opportunities
Performance work is not one-and-done: measuring, fixing and verifying create natural follow-on work inside an account you already own.
Customer outcomes
Fewer unresolved incidents and a measured before-and-after give your team something concrete to take back to the customer.
Fewer escalations
When a performance complaint lands, you have an experienced pair of hands to bring into the trace instead of absorbing the escalation alone.
How the co-branded engagement works
A partnership is not a referral. It is a way of delivering specialist work to a customer you already serve, with clear ownership on both sides.
Lead ownership
The account stays yours. You own the customer relationship and the commercial arrangement with them; we work as your specialist delivery partner behind it.
Collaboration
We scope the engagement with your team, not around it. Your developers keep ownership of the Optimizely codebase, and we hand over specific, scoped changes rather than creating a dependency.
Service delivery
Reignite performs the specialist work — instrumentation, runtime profiling, trace analysis and root-cause investigation — while your team remains the face of the engagement.
Customer communication
Who says what to the customer is agreed before the engagement starts, so the customer always knows who is responsible for what.
Reignite's technical differentiators
The commercial case only holds up if the work does. This is what we bring to an Optimizely engagement that a generalist team usually cannot:
Instrumentation
We capture evidence from the running system — production traces or a faithful load — instead of guessing from the outside.
Runtime profiling
We profile the live .NET process and read what it is actually doing, rather than theorising from the source.
Root-cause analysis
We follow the trace down to the call that is costing the time, and we tell you which problems are worth fixing and which are noise.
Incident response
When a performance incident is live, an experienced pair of hands on the trace shortens the path from symptom to cause.
Optimizely use cases and platform experience
These are the areas we go after first in an Optimizely engagement. They are the shapes that repeat across Optimizely CMS and Commerce implementations, and every one of them is grounded in the way the platform actually runs — ASP.NET on SQL Server, a content cache, a search index, and, on DXP, shared cloud infrastructure.
Content loading in a loop
A block or partial that loads content per item, called once per row, called once per page, multiplied by the catalogue.
Caching that is not actually caching
Output and object caching configured but bypassed by a personalisation rule, a visitor group, a query string, or an authenticated cookie.
Publish-time invalidation storms
An editor publishes, the cache invalidates broadly, and every node in the cluster rebuilds the same expensive content at once.
Search and navigation queries
Unbounded result sets, facets computed for results nobody will page to, and filtering done in application code after the index has already returned too much.
Commerce pricing and inventory
Price, inventory and promotion evaluation resolved per line item, per request, against the database, instead of once and in bulk.
The database underneath
Missing or unusable indexes, plan regressions under parameter sniffing, and blocking that only appears at production concurrency.
DXP capacity and scaling behaviour
On DXP you are sharing infrastructure and scaling on someone else's rules. Knowing which problems are genuinely capacity and which are your own code decides whether you buy a bigger instance or fix the site.
Every Optimizely implementation is different, but the shapes repeat. If your customer runs something else, ask us in the conversation — we will tell you honestly whether we are the right fit. The method we apply is described on the Optimizely performance engineering page.
Partnership models and commercial framework
- This page publishes no partner rates, revenue-share percentages, minimum commitments or exclusivity terms.
- The partnership model and the commercial terms are discussed with each partner in the inquiry conversation, based on the clients you serve and the work you want help with.
- Nothing on this page is a published commercial offer; it is a description of how we work together.
Our Affiliate Program is a separate customer-referral payout program. It is not the partner program described here, and its terms do not apply to a partnership. Learn about the Affiliate Program.
Qualification and onboarding
Tell us about your practice
Submit the inquiry form with a short description of your Optimizely practice and the customers you serve.
We review the inquiry
Our team reviews every partner inquiry and follows up at the work email you provide.
A conversation about fit
We talk through the clients you serve, the work you would like help with, and how we would work together.
A first co-branded engagement
We start with a scoped piece of work where the outcome matters to a customer you already serve.
Partner FAQ
Do we need our own performance engineering practice to partner?
No — that is the point of the program. We provide the specialist performance engineering expertise, and you keep the customer relationship and the services you already deliver.
Who owns the customer relationship?
You do. We work as your specialist delivery partner behind your relationship, and how the engagement is presented is agreed before it starts.
How does this differ from Reignite's Optimizely customer page?
The /Optimizely page is written for a business that owns a slow Optimizely site and wants it fixed. This page is written for the agency, implementation firm or solution partner that serves those businesses and wants specialist delivery capacity behind its own relationship.
Is Reignite an official Optimizely partner?
No. Reignite is an independent performance engineering consultancy. We are not affiliated with, sponsored by, or endorsed by Optimizely, and nothing on this page should be read as an official partnership or certification.
How are commercial terms set?
The partnership model and the commercial terms are discussed with each partner in the inquiry conversation. This page publishes no rates, revenue share, minimum commitments or exclusivity terms.
What does an engagement look like for our team?
It is measurement-first: we capture evidence, find the root cause, make or scope the fix, and re-measure. Your developers keep ownership of the Optimizely codebase throughout.
Become a Partner
Tell us about your Optimizely practice and the customers you serve. We review every partner inquiry and follow up at the work email you provide.
Thank you — we'll be in touch!
Your partner inquiry was submitted to our team. We review every partner inquiry and will follow up at the work email you provided.
Reignite Software Performance is an independent performance engineering consultancy. We are not affiliated with, sponsored by, or endorsed by Optimizely. "Optimizely" and "Episerver" are used here solely to identify the platform many of our clients run on, and remain the trademarks of their respective owners.
