Skip to main content
GullySystem
Technology

Business solutions for Software development companies

Explore software for work such as “MVP and product builds for funded startups”. Review each business function below, including when it fits and what to check before implementation.

Software development companies

How the business operates.

Your product is delivery. Revenue depends on each person’s invoiced hours and the additional work requested by the client that remains unbilled.

Project and SOW register

Record each client, the contract type, the rate card, the milestones and the team, so every project shows what was sold before any hour is logged against it.

Timesheets against the plan

Log hours by person, project and task, with billable and non-billable kept apart and the burn shown against the estimate as the project runs.

Allocation and bench view

Show who is on which project, at what share of the day, and who frees up when, so sales can quote with the real capacity in view.

Change request log

Capture each extra ask with its effort estimate and the client’s approval, so out-of-scope work becomes a priced line instead of a favour.

Milestone and hourly invoicing

Raise invoices from approved hours or completed milestones, with the tax invoice following each client’s billing cycle and currency.

Project margin report

Set revenue against the cost of the people who worked on it, by project and by month, before the books are closed.

Joining and exit access checklist

List the repositories, cloud accounts and client systems each person holds, and tick them off on the day they leave.

Release and deployment log

Every build pushed to staging or production is logged with its version, date and the engineer who deployed it. Rollbacks are noted too. The delivery head and the client’s technical contact use it when something breaks after a release.

Sprint demo sign-off record

Each demo to the client ends with a recorded decision on every story shown: accepted, returned or deferred. Names and dates are kept. The project manager points to it when a later scope argument starts.

Support retainer hours register

Clients on a monthly support retainer have a block of hours recorded against them, and each ticket draws from it. Unused and overrun hours show clearly. Account managers read it before renewal talks.

The records that hold the operation together.

  • Client and statement of work register. Hold every client, contact and signed statement of work. Billing model, rate card, hour cap, renewal date and payment terms are fields on the record, so the contract can be searched and reported.
  • Proposals and estimates. Build an estimate by role, grade and week from your own rate card. Keep each revision and the assumptions behind it, and convert the accepted one into a project.
  • Project plan and milestones. Lay out sprints, releases and client acceptance dates for each project. Milestones carry the amount payable on sign-off, so a slipped date shows its effect on billing.
  • Timesheets against the plan. Engineers log hours by project and task. Leads then approve them each week, and a project’s approved hours are compared with the planned hours for the same period.
  • Team allocation and bench. See who is on which project at what percentage, and who frees up on which date. Sales and delivery read one list when a new request arrives.
  • Change request log. Record each scope change with its estimate, its requester and its approver. Approved changes raise the project budget and the billable total together.
  • Milestone and time-and-materials invoicing. Raise an invoice from approved hours at the contract rate, or from an accepted milestone. Every line points back to the timesheet entries or sign-off behind it.
  • Currency and rate handling. Bill a client in its own currency while costs stay in yours. Rates, rate revisions and the date from which they apply are kept on the contract.

Operational bottlenecks to check

Scope changes are never billed

A client asks for one more screen in a call, and the team builds it. The invoice does not change.

Hours and invoices disagree

The tracker says one total, the timesheet another, and the invoice a third. Somebody reconciles them by hand.

Nobody sees the bench early

A project ends and four people are idle before sales knows. Allocation lives in a sheet.

Fixed-bid margin is a surprise

A project estimated at one effort burns far more, and the founder finds out at the final milestone. The loss is already booked.

Access outlives the employee

A developer leaves, and their repository and client logins stay open. No one owns the leaver checklist.

Follow the work across teams.

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

  1. 1. Proposal and estimate

    A prospect asks for a build. The team prepares an estimate by role and week, and the proposal goes out under one number. The accepted version is kept with its assumptions. Nothing is retyped.

  2. 2. Statement of work signed

    The signed contract is attached to a new project. Its billing model, rate card, hour caps, payment terms and named roles are entered as fields, not left inside the file. They can be reported.

  3. 3. Team allocated

    Engineers are assigned by the delivery head, a tester and a designer by percentage and dates. Clashes with other projects show before the allocation is saved.

  4. 4. Sprints and timesheets

    Sprints and milestones sit on the project calendar. Engineers log hours against the project and task each day, and the project lead approves them weekly.

  5. 5. Changes recorded and approved

    A request from the client becomes a change entry with an estimate. It is approved by the account owner and the client contact, then added to the project’s scope and budget. The client sees it.

  6. 6. Invoice and review

    Approved hours or accepted milestones become the invoice. At close, planned against actual hours and cost are compared and the project is archived with its documents. History stays searchable.

Roles and responsibility boundaries.

For the founder or managing director

Read project margin, idle cost, invoices raised and unpaid, and renewals due, without asking each delivery head for a sheet.

For delivery heads and project leads

Plan sprints and approve timesheets. Raise change requests and watch hours against the budget of every project you run.

For engineers, testers and designers

Log hours against the right project and task, see their own allocation, and apply for leave from a phone or a laptop.

For account managers and sales

Keep proposals, signed statements of work and renewal dates in view. Check free engineers before promising a start date.

For finance

Raise and chase invoices from approved hours and accepted milestones, and reconcile receipts to the project that earned them.

Reports your managers need.

  • Hours planned against hours logged, by project and by sprint
  • Free engineers with skills and free-from dates
  • Change requests raised, approved and billed, by client
  • Invoices raised and unpaid, by client and age
  • Margin by project, split into fixed-bid and time-and-materials
  • Utilisation by engineer, role and month
  • Statements of work and retainers due for renewal

Connections to scope

  • Issue trackers
  • Git hosting
  • Accounting software
  • Email
  • Calendar
  • Payment gateways
  • Bank statement files
  • Single sign-on

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.

Your rate card and grades

Junior, senior and lead grades, their client rates and their internal costs are entered as you price them today.

Billing models

Fixed bid, time and materials, capped hours, monthly retainer and dedicated team are each set up with the rules your contracts use.

Approval steps

The approver for each timesheet, change request and invoice is chosen per client or project type, and your delivery leads confirm the chain before launch.

Tracker connection

Hours or task counts are brought in from the issue tracker your team already uses, through a connection scoped during implementation.

Limitations to settle before implementation

  • A solo freelancer with one client can invoice from a simple template.
  • Teams that only need a code tracker for issues and pull requests, with no billing or contracts, should keep using that tracker.

Choose the operation you want to improve.

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

  • MVP and product builds for funded startups
  • Mobile apps for consumer and field teams
  • Custom business systems for SMEs moving off spreadsheets
  • Dealer, distributor and field sales apps
  • Dedicated development team engagements
  • Legacy system modernisation
  • IT consulting and technology audits
  • Support and maintenance retainers after launch
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