Skip to main content
GullySystem
Computers and IT · Software for enterprise software companies

Follow each enterprise deal from RFP to go-live, and every customer’s licence and support.

An enterprise software company sells slowly and supports for years. A deal passes through RFP, pilot and negotiation, then each customer runs its own version with its own changes and an annual support contract. The software we would build tracks the opportunity, the deployment, the licence and the SLA ticket on one customer record. Renewals and version differences stop depending on the account manager’s memory.

At a glance

A single customer may take months to buy and then stay for a decade. The money is in the licence, the implementation and the yearly support, and each of the three is tracked somewhere different.

A customer register built around your own contract terms is the base. It joins the sales pipeline to deployments and support, so the person answering a call knows what the customer bought and which version it runs.

How the work runs today

Sales answers an RFP, runs a proof of concept, and negotiates a licence with a statement of work for implementation. A project team then configures and customises the product at the customer’s site or on its cloud. Every customer ends up on a slightly different build.

After go-live, the customer logs issues under an SLA with severity levels, and support has to answer inside the committed response times. Patches and releases reach customers at different dates, and some customers are many versions behind. Annual support and licence renewals arrive on dates that sit in different people’s calendars.

Resellers and system integrators bring in some deals, and their margin and the end customer both have to be tracked.

Where it breaks

What goes wrong for enterprise software companies without a proper system.

Pipeline and delivery are disconnected

What sales promised in the RFP is not visible to the project team. Gaps surface at go-live.

Nobody knows who runs what version

A defect is reported, and support cannot say which customers have the affected build. Patches go out blind.

Support renewals lapse quietly

An annual support contract expires, and the customer keeps raising tickets for months. Nobody sends the renewal quote.

SLA breaches are found afterwards

A severity-one ticket sits unanswered over a weekend, and the customer raises it at the review meeting. The log shows it too late.

Customisation is untracked

A change built for one customer is not recorded against its contract. The next upgrade breaks it.

What the software does

What we would build for enterprise software companies.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Opportunity and RFP tracker

Follow each deal through RFP, proof of concept, commercials and approval, with the requirements promised held on the record that later becomes the project.

Customer and deployment register

Record every customer’s modules, version, environments, hosting and contacts, so a support call begins with what that customer actually runs.

Implementation project plan

Hold phases, owners, customer sign-offs and open dependencies for each rollout, with the status visible to the account owner without a call.

Licence and support contracts

Keep the term, scope, user or module count and renewal date of each contract, with a renewal list that opens ahead of the expiry.

SLA ticketing with escalation

Classify tickets by severity, start the response clock on arrival, and escalate to a named manager when a commitment is about to be missed.

Customisation and change log

Record each custom change against the customer and the version it was built on, so an upgrade plan knows what to retest.

Partner and reseller register

Link each deal to the partner who brought it, with the margin agreed and the end customer shown beside it.

Solutions inside

The business modules enterprise software companies use most.

Each one is also available on its own, or inside a system built for you.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, Tally reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions enterprise software companies ask before they call.

Can it replace our CRM and ticketing tools?

Sometimes, but not by default. Many companies keep their CRM or helpdesk and connect it. The register of deployments, contracts and versions is the part that usually has no home.

Does it deploy or patch customer installations?

No. It records what each customer runs and which patch they hold. Releases and deployments stay in your build and release tooling.

Can it store the signed contract?

Yes. The signed licence, statement of work and amendments are attached to the customer record. Whether a clause binds anyone is for your lawyer to say.

How long before it is in daily use?

It depends on how many customers, deployments and contracts are loaded and on how many tools are connected. A short discovery comes first, and the proposal then lists what is included.

What happens in the free technology audit?

We look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough to start. You get a report ordered by priority, and there is no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. The audit settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • No obligation
  • A reply within one business day
  • Your details stay private

All fields are required. A short description is enough.

Your details stay private. Privacy policyProtected by reCAPTCHA.