Skip to main content
GullySystem
Technology

Knowledge Base for SaaS and software companies

Publish approved answers and instructions that staff or customers can find.

Helpdesk

Does this function belong in your operation?

Use when recurring questions or procedures need a shared written answer.

A repeated question needs a maintained reference.

Help articles for onboarding steps, integration guides and billing questions sit in one place, linked from tickets. Support pastes the right article into a reply. Questions that keep returning become new articles.

Bring the records the workflow depends on.

  • Article topics
  • Review owners
  • Audience and access rules

Outputs to check

  • Approved article library
  • Article revision and owner register
  • Search and outdated-content review list

Follow the knowledge base workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Choose the question

    Identify a recurring issue and the intended audience.

  2. 2. Write the procedure

    Use verified steps and clear limits for the task.

  3. 3. Review accuracy

    Obtain the responsible subject owner's approval.

  4. 4. Publish with access controls

    Make the approved article discoverable to its permitted readers.

  5. 5. Maintain the answer

    Review changed systems and feedback, preserving revisions or withdrawing obsolete instructions.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Customer

Finds relevant approved instructions and raises a support request when the answer does not fit the issue.

Support executive

Sends the right article in seconds and does not type the same explanation again.

New technician

Reads how the senior technician does it before being sent alone to a customer’s site.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Article becomes outdated

Withdraw or flag it and assign an owner to review the changed procedure.

Answer does not fit the case

Escalate to a person instead of repeatedly presenting the same instructions.

Restricted article shared externally

Revoke the share and review whether sensitive information was exposed.

Can this work independently?

A knowledge base can operate independently as a controlled library. Support and ticket systems can link relevant articles, but a linked answer does not automatically resolve a customer's case. Access control separates public instructions from internal procedures or sensitive configuration details.

Systems and records it connects with

  • Ticket management: Numbered requests, ownership and resolution history.
  • Customer support: Customer conversations, unresolved questions and response history.
  • Helpdesk automation: Rule-triggered ticket assignments and escalation outcomes.
  • Your website: Permitted enquiries or booking requests with source references.

Configure, test and introduce the workflow.

  • You share recent tickets and calls. You get a list of article titles worded the way customers ask.
  • Every topic is handed to one person who looks after it, with a date for its next review. You get a sheet showing who looks after what. Ownership keeps it alive. Technicians draft the first articles with pictures and clips. We format them and you check the steps.
  • A search box is added to your website or ticket link. You test it with real customer phrases. Support staff attach articles in ticket replies. Searches that found nothing are reviewed to guide new articles.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Readers can find articles by relevant terms.
  • Restricted content stays within its audience.
  • Each published article has an owner.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • 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

Questions before implementation.

When should saas and software companies consider knowledge base?

Use when recurring questions or procedures need a shared written answer. A repeated question needs a maintained reference.

What should we bring to the requirements discussion?

Bring anonymised examples of Article topics; Review owners; Audience and access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Publish approved answers and instructions that staff or customers can find. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Instructions must be reviewed by qualified people where safety, health or regulated work is involved.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Readers can find articles by relevant terms. Use this check when reviewing the first working version.

Talk to us

Discuss knowledge base for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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