Skip to main content
GullySystem
Technology

Business solutions for SaaS and software companies

Explore software for work such as “Outbound to a named account list”. Review each business function below, including when it fits and what to check before implementation.

SaaS and software companies

How the business operates.

Your product ships code, and the business runs on accounts. Each customer is on a plan, has a renewal date, pays through a gateway and writes to support, and those facts live in different tools.

Customer and subscription register

Hold each account with its plan, seat count, add-ons, billing cycle and renewal date, so the list the team works from is the list finance bills from.

Trial and onboarding tracker

Show who started a trial, what they have used and who has been contacted, with a follow-up due before the trial ends.

MRR and churn report

Total recurring revenue by plan, new, expansion, contraction and cancelled accounts, built from the subscription register instead of a hand-made sheet.

Failed payment and renewal list

List accounts whose payment failed or whose renewal is near, with the contact, the last attempt and the follow-up that is due.

Support and bug triage

Log each request against the account, tag it as a question, a defect or a feature request, and group repeats so engineering can count the affected customers.

Account health view

Bring login activity, open tickets and payment status onto one page per customer, so success calls start from facts.

Internal admin console

Let support extend a trial, change a plan or pause an account from a screen with its own access rules and a log of each change.

Usage limits and overage log

Records each account’s seat, storage or call limits against actual use in the billing cycle. Customer success sees accounts near a ceiling. Overage lines pass to the invoice once approved.

Feature request voting board

Collects requests raised by customers and support, with the accounts that asked and their plan value beside each one. Product managers rank the board. Shipped work is announced to everyone who asked.

Uptime and incident history

Lists each outage or slowdown with its start, end, affected accounts and fix. Support quotes from it when a customer writes in. Credits owed are noted on the account.

The records that hold the operation together.

  • Account and subscription register. Hold every subscriber with its owner, workspace, plan, seat count, add-ons, billing cycle, start date and renewal date. Billing and success work from the same list.
  • Plans, add-ons and pricing rules. Define plans, seat tiers, usage allowances, annual discounts and add-ons once. Proration and the way annual plans count toward monthly revenue are agreed during set-up.
  • Trial and onboarding tracker. List trial signups with seats invited, features used and the sales or success person assigned. A follow-up falls due before the trial ends, not after.
  • Invoices and recurring billing. Raise an invoice for each cycle from the subscription record, with tax settings per country. Upgrades and seat changes mid-cycle produce the adjusted line on the next invoice.
  • Failed payments and card recovery. Record each gateway failure with the reason, the retry schedule and the owner. Send a card-update request to the account admin and list accounts still unpaid.
  • Renewals and cancellations. Show renewals by month with the contact and the plan. Log each cancellation with a reason from your own list, the last access date and any refund given.
  • Recurring revenue and churn report. Report revenue by plan as new, expansion, contraction and cancelled, plus logo churn and seat churn. Every figure drills down to the accounts behind it.
  • Support tickets and help articles. Log each request against the subscriber, set a priority by plan, and attach the help article that answered it. Repeat questions point to articles still missing.

Operational bottlenecks to check

Revenue numbers do not match

The gateway, the invoice list and the sheet each show a different monthly total. Nobody trusts the report.

Failed payments go unchased

A card expires, the retry fails, and the account is live for weeks without paying. Collections stay manual.

Trials end without a follow-up

A team that used the product daily lapses on day fourteen because nobody called. The lead is lost.

Churn has no recorded reason

Customers cancel, and the cause lives in an email thread. Product never sees a pattern.

Support and bugs share one inbox

A defect reported by three customers reaches engineering as three separate emails. Priority is a guess.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Signup and trial

    A visitor registers, and an account is created with the trial plan and its end date. Sales sees which signups used the product and who has been contacted.

  2. 2. Conversion

    A trial turns into a paid subscription with a plan, seat count, add-ons and billing cycle. Enterprise buyers get a contract with a negotiated price on the same record.

  3. 3. Billing and collection

    Invoices are raised for each cycle. Payments arrive from the gateway, failures are retried on a schedule, and unpaid accounts are listed for a person to follow up.

  4. 4. Support and success

    Requests are logged against the account and tagged as a question, a defect or a feature ask. Customer success reads usage and open tickets before every review call.

  5. 5. Renewal or change

    Upcoming renewals are listed ahead of the date. Upgrades, downgrades and pauses change the plan and the invoice together, with the effective date recorded.

  6. 6. Cancellation and learning

    A cancellation records its reason, the last day of access and any refund. Reasons are totalled by plan and by period for the product team.

Roles and responsibility boundaries.

For founders and finance

Read recurring revenue, churn, failed payments and renewals due from the subscriber record, then export the invoice list for the accountant.

For sales and customer success

Work trials, expansions and renewals from one list, and read usage and tickets before calling an account.

For support agents

Log and answer requests, tag defects, extend a trial or pause an account within the access you have been given.

For engineers and product managers

See grouped bug reports, the accounts behind each, and the cancellation reasons that mention a missing feature.

For account admins at the customer

Update the card, view invoices, change the seat count and download receipts from a self-service page.

Reports your managers need.

  • Monthly recurring revenue by plan: new, expansion, contraction, cancelled
  • Logo churn and seat churn, with cancellation reasons totalled
  • Trials started, converted and lapsed, by source and by owner
  • Failed payments open, by retry stage and age
  • Renewals due in the next 30, 60 and 90 days
  • Open bugs and feature requests ranked by accounts affected
  • Support tickets by plan, type and first response time

Connections to scope

  • Payment gateway
  • Product database or API
  • Email
  • Chat or messaging
  • Accounting export
  • Issue tracker export

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Plans and pricing rules

Your plan names, seat tiers, add-ons, discounts and the way annual contracts count toward monthly revenue are set up as you sell them.

Cancellation reasons and ticket tags

The reasons a customer can give and the categories of a request are your own lists, which you can extend later.

Gateway and product connections

Payment events are read from your gateway and usage from your product database. Your engineers and ours scope both connections together.

Currency and tax settings

Every billing country gets its own currency on the invoice, its own tax line and its own registration number. During installation, your finance lead reviews trial invoices alongside our team and corrects any wording.

Subscriber data moved over

Accounts, plans, open invoices and renewal dates come from your sheet and gateway export. A comparison report is checked before go-live.

Hosted by GullySystem

GullySystem hosts the system, so finance, success, support and engineering read one subscriber record.

Limitations to settle before implementation

  • A company selling one-off software licences with no recurring billing will find Enterprise Software Company Management Software closer.
  • A firm that runs other companies’ servers on contract is better served by Managed Service Provider Management Software.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Outbound to a named account list
  • Inbound speed to lead on demo requests
  • Free trial and freemium conversion to a demo
  • Seat expansion inside existing accounts
  • Renewal saves and churn recovery
  • Partner and reseller sourced pipeline
  • Webinar and event follow-up
  • Win-back of closed-lost deals
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements