OptiApps — The surface your team sees
Custom apps that live inside your CRM
Purpose-built panels embedded in SugarCRM, Pipedrive and Zendesk. Built on your own data model, released on your own schedule. Not another tab. Not another login.
- Embedded, not bolted on
- Your data model
- Versioned releases
- Shipped in weeks
Your team already has the CRM open all day. Every extra tool you buy them is another tab they forget to check, another login they lose, and another place the data goes quietly out of date.
How it works
Four steps from idea to live
An OptiApp goes live in four steps: we map your data model, build the panel, embed it in the CRM record page, then you promote it through draft, staging and published. There is no platform migration and no six-month discovery — we start with the one workflow that hurts most.
We map your data model
Your modules, your fields, your relationships. No generic object model to bend your business around.
We build the panel
A focused app that does one job well — a quote builder, a lookup, a timeline. Designed for the screen it sits on.
It embeds in the record
The app renders inside the CRM record page. Your team never leaves the screen they already work in.
You release it when you are ready
Draft to staging to published. Test on real records with a handful of people, then roll it out to everyone.
What embedded actually means
The app is part of the record page
Embedded means the app renders inside the CRM record page itself and reads the record it is sitting on, rather than opening as a separate tool. In the schematic below the greys are your CRM — its sidebar, its record header, its panels — and the cyan block is an OptiApp rendered in place.
Configure and price this deal
Illustration of an embedded panel. Layout and figures are examples.
On an opportunity
A quoting and CPQ panel that prices from your rules, not a spreadsheet.
On a quote line
Live stock availability pulled from the ERP while the rep is still typing.
On a ticket
A service-history timeline so the agent sees every prior job in one place.
On an account
A credit-status flag from finance, visible before anyone promises a delivery date.
Release channels
Draft, staging, published
Every app moves through three channels. A release is promoted forward, never rebuilt — what you signed off in staging is exactly what goes live.
- Draft
Work in progress. Visible only to the people building it.
- Staging
Real records, real users, a small group. Sign it off here.
- Published
Live for everyone. Rollback is one promotion away.
Capabilities
What you get in every app
Every OptiApp ships with the same foundations: it can render as a panel, a dashlet or a full page, it reads and writes your own custom modules and fields, it runs as the logged-in user, and each release is a numbered artefact you can promote or roll back.
Panels, dashlets and full pages
Sit an app beside a record, drop it on a dashboard, or give it the whole screen. Same app, different surface.
Your data model, not ours
Custom modules and custom fields are first-class. If it exists in your CRM, the app can read and write it.
Versioned releases
Every release is a numbered artefact. Promote it forward when it is ready, roll it back if it is not.
The user's own permissions
Apps run as the logged-in user. Nobody sees a record through an OptiApp that they could not open directly.
Talks to your other systems
Pull from the ERP, the accounting ledger or an internal API. The panel shows one answer, not four tabs.
Changed in an afternoon
Small change requests land the same week. No quarterly release train, no waiting for a vendor roadmap.
Straight answers
The questions buyers actually ask
Ownership, upgrades, and how an embedded app differs from customising the CRM itself — answered the way we would answer them on a call.
Is this just an iframe?
Yes, an OptiApp renders in a frame inside the CRM page, and that is deliberate. The app is served under your instance, authenticates as the signed-in user, and reads the record it is sitting on, so your team never leaves the CRM and never logs in twice.
What happens when our CRM upgrades?
Apps sit on documented extension points rather than in the core code, so an upgrade does not rewrite them. We test each app against the new version before you upgrade, and any fix ships as a normal release.
Who owns the app we pay for?
You own the app you pay for. It is built for your organisation on your data model, and you can take the source with you. We are not holding it hostage to keep you on a subscription.
Can our own developers work on it?
Yes — your own developers can build and release OptiApps. We hand over the repository and walk your team through the release channels. Plenty of customers have us build the first two apps and then take the third one themselves.
How is this different from customising the CRM directly?
Heavy customisation makes your CRM harder to upgrade and harder to support. An OptiApp keeps the custom logic in its own versioned artefact, so the CRM stays close to standard and the app can change without a platform project.
Bring us the screen your team hates.
Thirty minutes on the record page where the work actually stalls. We will tell you what an OptiApp would put on it — and what it would cost.
No obligation. No procurement process to start a conversation.