Skip to content
All solutions

SOLUTIONS

Software Houses & IT Companies

Run delivery, reviews and client support from one connected record — from the first task to the support contract after launch.

The common friction

Software work rarely ends at launch. Tasks move between developers, testers and leads; clients report issues; support periods begin and end. Somewhere in between, someone has to know what is covered, what is overdue and who owns the next step.

Where it usually hurts

  • Reviews and handoffs that live in chat threads
  • Support requests that arrive without an owner
  • Not knowing which projects are still under contract

How it can work in Viganium

Demo

Guided example. The steps are illustrative, not a client case study.

  1. 1

    A release task moves through development and review levels in a workflow.

  2. 2

    At launch, the project enters support under its contract.

  3. 3

    A client reports an issue on the portal; the support queue's two SLA clocks start.

  4. 4

    Finance issues the support period's invoice from the contract's schedule.

The modules that matter here

  • Projects

    Client or internal projects with an owner, members, status, priority and dates. A finished project takes new work only while a support contract covers it.

  • Tasks

    Assigned to a person, a whole department or a workflow, with comments, files, an activity history and reviews.

  • Workflows

    Work passed through people in levels: everyone on a level works at once, and the next level starts when they have all finished.

  • Tickets & SLA

    Client requests routed to the responsible department, each with two clocks — a View SLA and an Assignment SLA — plus warnings and a full history.

  • Client portal

    Clients sign in to their own portal to follow their tickets and their projects' tasks. Their accounts are kept apart from staff accounts.

  • Support contracts

    Support periods with a schedule, invoiced period by period and tied to the project they cover.

  • Invoices & payments

    Invoices for a client and, optionally, one of its projects. Payments are recorded against an invoice, each keeping the exchange rate of its own day.

Talk it through with us.

Explore whether Viganium System fits the way your company works, or whether a custom system makes more sense.

  • Use Viganium System

    Explore the existing platform and discuss how it could fit your company.

  • Build Your Own System

    Start with your processes, constraints and goals. Design the right software around them.