The CRM your reps don't have to switch to
The browser is still the install — it always was. The Glime desktop app is for the other eight hours: the call you are already on, the meeting already on the room display, the quote you are building on a train with no signal. Same records, same pricing engine, same approval chain, in something that is allowed to behave like an application.
Version 2.0.0 · Windows 10 or 11, 64-bit · Included in every plan and in the free trial · Signs in to the workspace you already have
Three things a browser tab structurally cannot do
Not "nicer scrolling". These are the three moments where a CRM in a tab quietly loses — and all three are moments this product is supposed to own.
Log the call without leaving the call
Ctrl+Shift+Space anywhere in Windows opens a small overlay on top of Zoom, Teams, Outlook or a browser: log a call, add a contact, create a lead, look up an account, start a quote. It closes back to whatever had focus. CRM data rots because the price of recording a call is abandoning it — this is that price removed.
Keep the account card above everything
A small always-on-top companion window, pinned for the meeting: who you are talking to, their open quotes and where each sits in its approval chain, last activity, renewal date, and a note field that writes straight to the record. A tab cannot float above another application, so the web version of this is a second monitor with no context on it.
Present a quote without presenting your margin
Plug into the room display and the customer's copy of the quote goes full-screen, while cost, margin, floor price and the approval chain stay on your laptop. It renders the same payload the customer's share link serves — field by field, built by the server — not your screen with columns hidden in CSS.
Get it on your PC
One installer, about a minute, no administrator rights needed for a per-user install. On first launch, pick demo workspace to explore the whole product with sample data on your own machine, or connect a workspace by its address and sign in with the account you already have.
Glime-CRM-Setup-2.0.0.exe · Version 2.0.0 · Windows 10 (1809 or later)
or Windows 11, 64-bit
| Operating system | Windows 10 version 1809 or later, or Windows 11 — 64-bit (x64) |
|---|---|
| Disk | About 400 MB, plus the local cache for the records you actually open |
| Memory | 4 GB works; 8 GB if you keep six-figure lists open in the grid |
| Rights to install | None — it installs per user by default. Per-machine and silent install are available for IT |
| Account | Your existing Glime sign-in, or the built-in demo workspace with no account at all |
| Price | Included in every plan and in the free trial |
| Updates | Checked daily and on demand, downloaded only when you ask, installed when you quit |
Verify the download if you like: run
Get-FileHash .\Glime-CRM-Setup-2.0.0.exe in PowerShell and
compare it with the SHA-256 published beside the installer on the
release notes. We publish the hash there rather
than on this page so it is written at release time, by the thing that built
the file.
The same product, rendered by something allowed to be an app
A rep building a quote line by line and an approver clearing a queue are exactly the people who live in one application all day. So the desktop app draws its own chrome instead of putting a web page's chrome in a window.
Tabs, windows, and tear-offs
A quote in one window, the account it belongs to in another, the approvals queue on the second monitor. Tear a tab off, drop it back, and find every window where you left it after a restart.
Split panes that keep the list
Master–detail: the list stays on the left while you work the record on the right, so clearing twenty quotes is twenty clicks, not twenty rounds of back-navigate-and-find-your-place.
A palette that knows your workspace
Ctrl+K searches records, not just menu commands, against a local index — accounts, contacts, quotes and every action, ranked, in a quarter of a second.
A grid that takes a hundred thousand rows
Resize, reorder, pin, multi-sort, group, edit in the cell, and change two hundred rows at once — with every cell still asking the field rules who is allowed to see and change it.
The quote editor as a workspace
A full-height line grid with a live margin and approval-band gauge: as the discount is typed, the rep sees which rung the quote is about to land on and who will have to sign it — before they promise it out loud.
Approvals in the tray
A badge count of what is waiting on you, and a popover that approves or rejects with a reason without opening the main window. The chain, its order and its clock are drawn; they are still decided by the server.
Keyboard-first, with a map
One shortcut registry drives the menus, the palette and the help sheet, so the cheatsheet cannot drift from the app. Nothing is a shortcut only a support article knows about.
Native PDFs and drag-and-drop
Print or export a quote as a real PDF from the same template the web renders. Drop a CSV on the window to start an import, drop a file on a record to attach it.
Several workspaces at once
Consultants and partners keep more than one. Each gets its own session,
its own cache and its own sign-in, so switching never signs the other one
out, and glime://quote/… links open the right one.
Numbers, and where they were measured
A local cache in the app's own background process — the records you use, on your disk — is why the desktop app answers before the network does. These figures come from the performance suite that runs in our CI on every change, against a hundred thousand rows.
These are the worst figures from the slowest machine our CI has run this on — two shared cloud runners measured the same list paint 1.8 s apart, so quoting the faster one would be picking a number rather than reporting one. Cold start to a usable window is 5.8 s on that same worst run. A real laptop, with its own disk and a GPU that is not emulated in software, comes in well under all of it. The two figures above that belong to our code rather than to the machine — the search and the grid's render cost — barely move between boxes, which is exactly why those are the ones the build is failed over.
Offline that tells you the truth
The failure mode of every "works offline" CRM is the optimistic one: it shows you a state the server never agreed to, and you find out three days later that the note you typed on the plane does not exist. Glime does the honest version.
- Reads keep working, and say how old they are. Every cached screen carries its own "as of" — you always know whether you are looking at this morning or last Tuesday.
- Writes are queued, and say they are queued. A queued note, edit or quote is visibly pending, never dressed up as saved.
- The queue replays the same requests. When you reconnect, the app sends exactly the API calls it would have sent live — so the server applies the same rules, in the same order, with the same refusals. There is no second "offline mode" write path to disagree with the first.
- Approvals are never decided on the laptop. You can read the queue and prepare a decision; the decision itself is the server's, with role, chain order and the self-approval refusal intact.
- Quote maths is the same maths. The pricing and CPQ engine in the desktop app is the same code the browser runs, so a quote priced on a train prices identically when it lands.
A laptop is a threat model, not a detail
Putting customer data on a machine that travels is a decision, and it is only a good one if the machine is treated as something that gets lost.
Token in Windows Credential Manager
The session token lives in the OS keychain, held by the app's background process. The page code holds an opaque handle and never the token, so there is nothing in the renderer for a hostile page to steal.
The cache is sealed
The local copy of your records is encrypted with AES-256-GCM under a key from the keychain. A copied cache file, off the machine, is a file of noise.
Idle lock and panic wipe
It locks itself after an idle timeout and when the machine sleeps. If a laptop goes missing, one panic wipe destroys the cache, the queue and the session on the spot.
Revoke reaches the laptop
Revoke the session server-side and the next time that machine connects, its key, cache, queue and session are destroyed. It takes a connection — we would rather say that than imply we can reach a laptop in a drawer.
It only talks to your workspace
Network egress is pinned to your own server and blocked everywhere else, so a page inside the app cannot quietly call somewhere it should not.
Masked stays masked
A field a role may not read is not merely hidden on screen — it cannot be copied out of the grid or an export either, because the value is not there to copy.
No new door in your firewall
The app talks to your workspace server the way a browser does, over HTTPS, outbound. There is no inbound port, no agent, no extra origin to allow-list.
The audit trail is the same trail
Everything done here is written to the same server-side audit record as the web app — and the audit trail and the export are never behind a plan, on any client.
The desktop app re-renders everything and re-decides nothing
Most desktop clients are a second implementation of the product, and they drift. Ours is the same implementation in a different frame — which matters here more than anywhere, because the thing that would drift is the discount policy.
- One pricing engine. Prices, currencies, price books, tax, ramps and terms are the same code the web app loads. Not a port of it.
- One approval chain. Bands, triggers, delegation and the SLA clock are decided by your server, which refuses an out-of-order step and refuses a rep approving their own quote — whatever any client asks for.
- One field-rule table. The grid asks who may see and change each field before it draws a cell, using the rules your admin set once.
- One entitlement answer. What your workspace bought is settled server-side; installing something cannot unlock a feature.
- Parity is tested, not promised. A CI check compares the screens the web app can reach with the screens the desktop app can reach and fails the build on a gap. "Everything is in there" is only worth saying if something breaks when it stops being true.
Which is also why nobody has to choose a client. The same person can quote on the desktop at their desk, approve from a phone browser in a taxi, and see one consistent workspace — because there is one product underneath both.
Rolling it out to a fleet
Five hundred seats should be a configuration, not five hundred conversations.
| You want to | How |
|---|---|
| Install without a person present | Glime-CRM-Setup-2.0.0.exe /S, with /D=C:\Path to choose the folder |
| Point every machine at your server | A JSON policy file at %ProgramData%\Glime\policy.json naming the workspace — it is applied at launch |
| Pin settings like the idle-lock timeout | The same policy file, with locked to make the pinned settings read-only in the app |
| Control when updates reach people | Host your own update feed and name it in the policy file; staged rollout is a property of what you publish to it |
| Keep credentials out of the image | Nothing to do — the policy file drops any token or secret field it finds, and sign-in is always the person's own |
| Let one person hold several workspaces | Supported by design: separate session, cache and sign-in per workspace |
Deploying under management and want the policy file's exact shape, or a build signed with your own certificate for your software allow-list? Ask us — that conversation is a short one.
What the desktop app does not do today
The same list a competitor would leave off. You will find out in week one anyway, and finding out from us is cheaper for both of us.
- No macOS or Linux download. Windows is the only published build. Everyone else uses the web app, which is the whole product.
- No Windows Hello step-up on an approval. Approving in the desktop app is exactly the web's approval — role-gated, ordered, server-decided. Signing an approval with a device key is designed and not built, and it will add a factor and an audit fact, never become the gate.
- No mailbox or calendar matching. Activities are logged by a person, including through quick capture. Reading Outlook on the device and matching it locally is the plan; nothing pretends to do it now.
- No desktop-only reports or dashboards. Reporting belongs to the product, not to one client, so it lands for everyone or not at all.
- Installers are not code-signed yet. Until they are, Windows SmartScreen may warn on first run. Check the hash on the release notes before you click through a warning — on any download, from anyone.
What ships and what changed is on the changelog, the same place the web app's releases are recorded.
Questions people ask before installing
Does the desktop app cost extra?
No. It is included with every plan and with the free trial, and it signs in to the workspace you already have. There is no desktop licence, no per-seat surcharge, and no feature that exists only if you install it — the desktop app renders the same product the browser does.
Which versions of Windows are supported?
Windows 10 version 1809 or later and Windows 11, 64-bit (x64). There is no 32-bit or ARM64 build, and macOS and Linux builds are not published yet. If you need one of those, say so — demand is how the order is set.
Do I have to install it to use Glime?
No, and most teams run both. The web app is the whole product and always will be; the desktop app adds quick capture, the floating call card, presenter mode, offline work and a grid built for very large lists. Installing changes where you work, not what you can do.
Can I use it offline?
Yes, for reading and for building quotes. Cached records stay readable and say how old they are, writes are queued and marked as queued, and when the connection returns the queue replays exactly the requests the app would have sent live. Nothing is shown as settled until the server has agreed to it, and approvals are never decided on the laptop.
Can the desktop app change a price or approve a discount on its own?
No, and that is the design. It loads the same pricing and CPQ engine the web app runs, and asks the same server for every approval. No price, approval step, field rule or entitlement is computed in the desktop code, and a CI check fails the build if the desktop shell cannot reach a screen the web app can.
What stops a customer seeing our cost and margin in a meeting?
Presenter mode renders the customer-facing payload the share-link route builds — the same field-by-field view a customer gets from a quote link, which never carries cost, margin or internal reason codes. It is not your window with columns hidden by styling, so there is no state in which the internal numbers are one scroll away from the room display.
What happens if a laptop is lost?
The local cache is encrypted with AES-256-GCM under a key in the Windows Credential Manager, and it locks on idle and on sleep. Revoke the session and the next time that machine connects, its key, cache, queue and session are destroyed. A machine that never connects again keeps a sealed cache it cannot unlock without the keychain entry — and full-disk encryption is still worth having, on any laptop, for any product.
How does it update?
It checks daily and when you ask it to, never downloads without being asked, and installs when you quit. If your IT team hosts its own update feed, they decide what reaches which machines and when.
Put it on the machine you actually sell from
Install it, open the demo workspace, and press Ctrl+Shift+Space while you are in something else. That is the whole pitch, and it takes a minute to disprove.
Version 2.0.0 · Windows 10/11, 64-bit · Included in every plan · Not on Windows? The web app is the whole product.