Skip to content
Log in Sign up

Early access is open

One trustworthy record of the work, the hours, and the approvals.

LynxSprint puts projects, work items, time, approvals and reporting on one permission model. Built for organizations where labour is the main cost and billable time has to be right.

Sign up See how it works
Permission codes
112
Record-level scopes
7
Surveillance features
0

Work management usually runs across four or five tools that never meet

A project tracker, a spreadsheet timesheet, a helpdesk inbox, an HR system, and a dashboard stitching them together. The gaps between those tools are where the numbers stop being true.

Five disconnected tools with lossy seams between them A project tracker, a spreadsheet timesheet, a helpdesk, an HR system and a reporting dashboard sit apart from one another. The gaps between them are marked as the places where time, attribution and cost data are lost. Tracker Timesheet Helpdesk HR system Dashboard
Each marked point is a seam: a place where an hour is logged against nothing, a cost is guessed, or an approval leaves no record.
  • Time sits apart from the work it describes, so utilization and project cost are estimates.
  • Timesheets get chased by hand, which costs a manager hours a week and still arrives late.
  • Approval happens in a chat thread, so a dispute six months later is an archaeology exercise.
  • Permissions are coarse, so accounts accumulate access nobody intended to grant.
  • Time zones and daylight saving corrupt duration maths quietly, twice a year.

A week of work, attributed as it is entered

Hours land against an activity always, and against a project and a work item whenever that is useful. The week moves into approval as one unit, and what it cost is a fact the moment it is entered rather than a figure someone reconstructs at month end.

A week in the LynxSprint timesheet grid A design representation, not a screenshot. Rows of work run down the grid and the five working days run across it, with hours in each cell. The four rows are Development and Code review against a client project and its work items, Meetings against internal work, and Administration against no project at all, because project and work item attribution is optional on every entry. A filled dot marks a billable row and a hollow one marks a non-billable row. Each day totals eight hours and the week totals forty. The week is in draft and can be submitted for approval. Week of 13 July Europe/London · business dates Draft Submit for approval Activity and attribution Mon Tue Wed Thu Fri Total Development Client project · ALPHA-142 6 5.5 6 4 3 24.5 Code review Client project · ALPHA-137 1 1.5 2 1 5.5 Meetings Internal 1 1 1.5 1 1 5.5 Administration No project or work item (optional) 0.5 1 3 4.5 Daily total 8 8 8 8 8 40 Design representation Every cell stores a UTC instant, an IANA time zone and a business date
A design representation of the weekly grid, not a screenshot of the product. It shows the shape of the model: activity is required on every entry, project and work item are not, and the week moves as one unit into approval.

A week in three steps

The same record carries through all three, which is what makes the reporting at the end of it worth reading.

  1. Step 1: Record the time

    Start a timer in one click, or enter a duration by hand. An entry needs a person, a date, a duration and a category. A project or work item is offered on every entry and demanded on none.

  2. Step 2: Submit the week

    The weekly grid shows what is recorded against expected hours, with the schedule and holiday calendar already applied. Anything missing is flagged before submission, not chased afterwards.

  3. Step 3: Approve and lock

    Managers approve a week for their reports in one screen. Approved time becomes read-only, and every decision leaves a permanent record with who made it and when.

One model, so the gaps have nowhere to open up

Projects, work items, time, people and reporting share one identity model, one permission model, and one audit trail.

  • Time that survives an audit

    Durations come from UTC instants stored with an IANA zone and a business date. Overnight shifts and daylight-saving changes are arithmetic, not the twice-yearly defect they are in most systems.

    Read more about Time that survives an audit

  • Approvals you can defend

    Draft, submitted, approved, locked, with a permanent decision log at every step. Approved time is read-only. A correction is a new attributable event, so nobody rewrites history quietly.

    Read more about Approvals you can defend

  • Permissions that match your org chart

    A granular permission catalogue with seven record-level scopes. Managers see their reports, group leads see their groups, and reporting lines are real records rather than an assumption.

    Read more about Permissions that match your org chart

  • Work and time in one model

    Time entries point at the same projects and work items your team plans against. Attribution is available on every entry and required on none of them.

    Read more about Work and time in one model

Our position

LynxSprint tracks work, not people

This is a constraint on what we build, not a setting an administrator can change. Naming the category is the only version of this promise that means anything.

It is also practical. People who trust the tool fill it in honestly, and honest input is the only kind that makes a utilization number worth reading.

Read our privacy stance

Features we will not build

  • Screenshot or webcam capture
  • Keystroke or mouse-movement logging
  • Application or website usage surveillance
  • GPS and device location tracking
  • Covert or notification-free monitoring
  • Productivity scores built from activity telemetry
AI

A permission-bound colleague, not an oracle and not an autopilot

AI is an organization-level opt-in and it is off by default. Every workflow completes with it disabled. An agent reaches the intersection of what you can see, what the agent declares, and what your organization allows, and nothing consequential happens without someone approving it.

How our AI works, and what it will never do

Built for organizations where labour is the main cost

Software consultancies, digital agencies, IT managed-service providers, engineering and architecture practices, and internal platform teams reporting capitalized time.

Who it is for, and who it is not

Start with one real week

Log a week of your own hours and put it through approval. That is a better test than any feature table, and it takes an afternoon.
Sign up See pricing