Skip to content
14-day free trial, no card9 languages176 business types · 50 apps
EN· USD
Try a live demoStart free trial

Software development company with zmle: how it works

A software house plans projects by milestone with tasks for each developer, records developer hours per project and bills time-and-materials work from the timesheet, quotes change requests and gets them accepted online before work starts, logs bugs and support requests after launch as tickets and bills monthly support and hosting plans with recurring invoices.

Lesson 19 of 22 · How it works

  • about 3 min
  • Operations → Timesheets

How it works

  1. Pick «Software Development Company» at sign-up: «Projects & timesheets» and «Finance» come on; «Customer support», «Sales pipeline A board that shows every open deal in the step it has reached, for example new, quoted, negotiating. You drag a deal to the next stage as it moves on. More words in the glossary» and «Letters & certificates» are recommended.

  2. The site builder's studio website shows your services, the «Projects» case studies and a brief form; a brief becomes a Deal A sale you are trying to win. It has a value, a stage and an expected close date. In the end you close it as won, or as lost with a reason. More words in the glossary in «Sales pipeline» from inquiry to signed proposal.

  3. «Quotations A priced offer for a customer. The customer gets a link, reads it online and can accept it there. More words in the glossary» sends the proposal or statement of work; on acceptance the project opens in «Timesheets» with milestones, a budget and tasks per developer on the board; «Letters & certificates» prints the NDA.

  4. Developers log hours per task; fixed-price milestones are invoiced from the project as they are marked done, time-and-materials work from «Unbilled time»; a change request is quoted, accepted online and added to the project.

  5. After launch, bugs and requests come in as tickets in «Support» with priorities and a customer portal; support and hosting plans bill monthly through «Monthly retainer plans».

  6. Reports: billable hours vs available, budget used per project, open tickets by priority and days to close, monthly recurring revenue.

Where to find it

Settings that change it

Checklist

Before you move on, check that you can:

  • Open Operations → Timesheets
  • Pick Software Development Company at sign-up: Projects & timesheets and Finance come on; Customer support,…
  • The site builder's studio website shows your services, the Projects case studies and a brief form; a brief…
  • Quotations sends the proposal or statement of work; on acceptance the project opens in Timesheets with…
  • Developers log hours per task; fixed-price milestones are invoiced from the project as they are marked done,…

Tips and common mistakes

  • Quote every change request, however small — accepted online it becomes a billable line nobody argues about later.
  • Set a budget alert on fixed-price projects; the warning comes before the hours exceed the price.
  • Code hosting and build pipelines stay in your developer tools; connect them to tickets through the API and webhooks.