How billing works

Exactly how your time is counted

You pay $50 for each billable hour, once a week. Here is how those hours are worked out, in plain words.

1. What time counts

Two kinds of time are billed:

  • Automated build time. This is recorded automatically while our automated development systems work on your project. Waiting time isn’t counted.
  • Developer time. Our developers record the time they work on your project, each period rounded up to the half hour. The total for the week is then rounded up to the next whole hour.

Sometimes several automated processes run at once to get a job done faster. That still counts as automated build time once, by the clock, not once per process.

2. How automated build time is rounded

Automated build time is counted in sessions, and each session is rounded up to whole hours. Work that starts again before that rounded hour runs out joins the same session, so short bursts close together aren’t each charged a full hour.

  • Five short bursts of work inside one hour: 1 hour.
  • Five bursts chained one after another across four hours: 4 hours.

A worked example

  1. 9:00 – 9:20Our automated systems work on a task. A session starts at 9:00.
  2. 9:40 – 10:10Another task starts before 10:00, so it joins the same session: 9:00 to 10:10. That’s 1 hour 10 minutes, rounded up to 2 hours, which covers until 11:00.
  3. 10:30 – 10:45Starts before 11:00, so it joins too. Still 2 hours.
  4. 11:15Starts after 11:00, so a new session begins (at least 1 more hour).

A session is billed in the week it starts in.

3. When both run at the same time

Developer time and automated build time are counted separately and added together. If both run on your project during the same hour, that’s two billable hours: one of developer time and one of automated build time.

4. The billing week

  • The week runs Sunday to Saturday, New York time.
  • On Sunday, the system prepares a bill for the week that just ended, from the time records.
  • We review it (and correct it if something was recorded wrong; every change is logged).
  • When we approve it, the card you saved at setup is charged.

You agree to these weekly charges when you pay the setup fee and save your card.

5. What your invoice shows

One line: “Development services”, with the amount. It doesn’t list the separate hours or sessions.

Example: 5 billable hours in a week × $50 = an invoice for $250.

If you think an invoice is wrong, tell us in writing at info@shtim.us within 7 days of the invoice date. After that, the invoice is final.

6. If a payment fails

Work on your project pauses automatically and you get an email. Work starts again only when the balance is paid and we switch the project back on.

7. Your client portal

Your client portal shows your project’s status, your invoices and your downloads. We may post updates when there is something to show, at our discretion.

8. Getting your code

  • New code is released when your balance is $0: as a ZIP download from your portal, or by handing over the repository.
  • The files you sent us are never held back, whatever your balance.
  • Once paid, you can use, change, sell and share it as you like. Shtim keeps the same right to reuse what it builds.
  • Shtim’s own working tools are left out of what you receive.

9. What we don’t do

  • No hosting. Shtim doesn’t host your finished project.
  • No completion promise. There’s no fixed price or guaranteed finish date; you pay for time worked.
  • No ongoing support is included.
  • We can decline, pause or stop any project at any time.
  • No refunds of the setup fee. It is earned once paid. Development hours are only billed after they are worked.

The full rules are in the engagement terms. Questions: info@shtim.us.