We’re preparing Billisecond Timers for its first release. The focus is on recording time against clients and matters, keeping descriptions with the work, and making it easier to check those entries before they reach an invoice.
It’s also the first part of a broader approach to business software at Experdition: applications that keep your working data on your own server.
Time records that are useful beyond the timer
Starting and stopping a timer is straightforward. What matters afterwards is whether someone can tell what the time was spent on.
Billisecond Timers records time against the relevant business, client and matter, with a description attached to each entry. The timesheet gives users a place to review their hours, correct descriptions and check entries before reporting or billing.
That review step is important. A running timer doesn’t replace a clear record of the work, and a list of hours isn’t much help if the person preparing an invoice has to chase down what each entry means.
For the initial release, we’re concentrating on that everyday workflow: recording the work, reviewing it and keeping the records organised.
Your data stays on your server
Billisecond Timers is a Windows application that uses an organisation-managed SQL Server database. Your time records, clients and matters are stored there—not in a shared Billisecond cloud service.
That means the database can sit within your existing IT environment, under your organisation’s control. Access, backups and ongoing database management remain part of that environment.
It also means installation needs some planning. Before supplying the installer, we’ll confirm the SQL Server setup, how workstations will connect and who will look after backups. The installer will be supplied by request so those requirements can be discussed first.
This is a deliberate choice. Not every business wants another hosted service holding its operational records. For organisations that already manage their own systems, software that works with that infrastructure can be a better fit.
The account used to manage a software licence is separate from the database holding the organisation’s working records.
What we’re checking before release
Preparing a release involves more than producing an installer.
We’re working through the installation instructions, database configuration, licensing and the steps someone will follow when they first open the application. Those instructions need to make sense to someone who hasn’t been involved in development.
We’re also reviewing how the application handles everyday interruptions: an unavailable database, an incorrect connection setting or a workstation that cannot reach the server. Users need a useful explanation and a clear next step when something goes wrong.
The website is part of that preparation too. Product information, licence purchases and account management need to follow a sensible path, with clear information about what is included and what is required to run the software.
Getting started with Billisecond Timers
We’re focusing on getting Billisecond Timers ready and making the setup process clear.
If you’re considering Billisecond Timers for your business, contact Experdition to discuss your Windows and SQL Server environment. We can confirm the requirements before you arrange an installation.