Automated timesheets for software agencies.
Logless reconstructs a useful draft of your team's working week from the development activity they already generate — reducing timesheet administration while helping agencies capture billable work that might otherwise go unlogged.
No sign-in, no GitHub connection, no email — see the whole product in under a minute.
Illustration: a fictional developer week. 58 GitHub events become draft timesheet entries totalling 31.5h; quiet stretches are flagged as potential missing work; the developer adds 4h and approves 35.5h.
Commit, pull request and review events from Jordan's week. Logless reads their titles and times, never the code.
Fictional week, drafted by the real Logless engine.
The problem isn't that developers don't work. It's that some of the work never makes it into the timesheet — a PR review here, a client call there, small pieces of work between the larger tasks. Individually forgettable. Collectively, real lost revenue.
Logless points out the quiet stretches in a week. You decide what they were.
Each developer connects their own GitHub account in a couple of clicks. Logless reads commit, pull request, review and issue metadata — never file contents or diffs.
Events are grouped into draft entries by day and project, described from your own commit titles. Quiet stretches of the working day are flagged as potential missing work.
Edit anything, add what GitHub couldn't see, then approve. Only then does your manager see the week.
The draft comes from a small set of fixed rules, not a black box. The same activity always produces the same draft.
Logless understands the work — not the code. The system is built around lightweight development activity and data minimisation: repository names and identifiers are never a normal part of what you or your manager see.
What Jordan sees
The draft, with the detail behind it
3 commits, 1 pull request — Checkout: per-currency basket totals
Added from a quiet stretch, 10:25–12:30
4 commits, 1 PR review, 1 pull request — Portal: usage chart
What a manager sees
Only after Jordan approves
No draft weeks, no activity feed, no repository names.
Logless does not use:
When someone adds time from a missing-work suggestion, Logless counts it as recovered and values it at that project's billing rate. Managers see it as an estimate, never a guarantee. Try your own assumptions:
Potential monthly billable work you might otherwise miss
£0
≈ 78h/month, based on the assumptions above
An estimate based entirely on the numbers you enter above — not a guaranteed or measured result, and not based on your actual team's data.
Logless is opening up gradually to UK software agencies and consultancies. Tell us a little about your team and we'll be in touch — no automatic emails, no mailing list, just a real reply when there's a fit.
Planned pricing
£8 per user per month
Indicative only, subject to change before general availability. Unlimited clients and projects.
Free for teams in early access.
No. Logless doesn't watch what you do — it reads commit, pull request and issue metadata from tools you connect, then drafts a timesheet you review and correct. It understands the work, not the code, and repository names never appear in a normal timesheet view.
Metadata about your own commits, pull requests, reviews and issues: when they happened, what type they were, which repository they belong to, and their titles. The titles become the first draft of your entry descriptions, which you can edit before approving. Logless never fetches file contents, source code or diffs. One honest caveat: GitHub's standard permissions have no read-metadata-only option for private repositories, so the access you grant technically allows more than Logless uses. A narrower GitHub App is on the roadmap.
Every draft is fully editable. Change the hours, rewrite the description, move it to a different project, or delete it — nothing is final until you approve it. GitHub can't see meetings, planning, or client calls either, so there's always a quick way to add what it missed.
GitHub is the focus for the current release, since it's where most billable engineering work already leaves a trail. Jira, Linear, GitLab and others are on the roadmap, not built yet.
No. Managers see a week's hours once you approve it, and can export the approved entries, including the descriptions you signed off. They never see draft weeks, your raw activity feed, or which repositories you worked in.
Traffic is encrypted in transit, and stored secrets like GitHub tokens are encrypted at rest. Every query is scoped to your company, so one company can never read another's data, and access within a company is restricted by role. Customer-managed encryption (BYOK) and stronger AI data guarantees are on our security roadmap — see our full security architecture for exactly what's built today versus planned.
Request early access, or try the interactive demo right now — no sign-in, no GitHub connection, no email required.
Already have an account? Sign in