Skip to content
Private beta

Know where the hours went.

Diurna is time tracking, expenses and profitability reporting for small studios. Track time in a week grid built for people who actually fill one in — then find out what a project really cost.

No credit card, because there's nothing to buy yet. We'll email you when Diurna opens up.

We fill one in too

Built by a studio that bills its own hours on this grid.

Small studios, not enterprises

Budgets, cost rates and utilization — no seat sprawl.

Talks to Claude

An MCP server instead of a chat box bolted on the side.

Track

A timesheet people will actually fill in

  • Week grid with spreadsheet-style cells, per-cell notes and a running total.
  • Copy last week's rows in one click, or add a row as you go.
  • A timer in the sidebar that follows you around the app.
  • Day view when you want to write a longer note against an entry.

Spend

Expenses, with the receipt attached

  • Weekly expense list with your own categories.
  • Receipts stored privately and served through signed links.
  • Billable and invoiced flags that flow into reports and invoices.

Report

What the project actually cost

  • Profitability: billable value measured against hours × cost rates.
  • Quarter, calendar year, fiscal year and all-time presets.
  • Rounded and raw hours side by side — no arguing about which is which.
  • Client report links: read-only, no login, revocable at any time.

Bill

Invoices and estimates, then out to Xero

  • Uninvoiced billable time becomes invoice lines at the right rate.
  • Estimates that convert to an invoice when they're accepted.
  • Xero hand-off by CSV or copy-paste — matched to Xero's import template.
  • Entries get stamped and locked once invoiced, so nothing is billed twice.

Ask your timesheets a question

Diurna ships an MCP server, so Claude can query your tracked time directly — no exports, no copy-paste, no chat box bolted onto a reports page. Connect it with one URL: it signs you in and acts as you, within your own permissions.

Things you can ask

  • “How many hours did we log on SearchX in July?”
  • “Which projects went over budget last quarter?”
  • “Create a client report link for last month, with amounts.”
  • “What's still uninvoiced across all clients?”
  • “Log 2.5 hours on the SearchX retainer for this morning's workshop.”
  • “Move yesterday's Admin hours on Merrimac Park to Design.”

Tools it exposes

  • query_time_entries
  • report_summary
  • uninvoiced_summary
  • profitability_summary
  • list_invoices
  • log_time
  • update_time_entries
  • start_timer
  • log_expense
  • record_invoice_payment
Connect Claude to Diurna →

FAQs

Questions we get asked

Mostly about when, how much, and what happens to your data. If yours isn't here, email us — a person answers.

When does it open?

We haven't announced a date, and we'd rather not invent one. We're finishing the version that handles several studios on the same instance; that is the last thing between here and opening the doors. The waitlist gets told first.

What will it cost?

Undecided. The plan shapes are settled — you can read them on the pricing page — but the numbers are not, and we're not going to print a figure we might retract. Waitlist members hear the price before it goes public.

Can I bring my history across?

Yes. The importer brings clients, projects, tasks, people, tracked time, expenses and receipts over, and it's idempotent, so running it twice won't duplicate anything. Today it runs as a script we run with you during onboarding; an in-app version is on the roadmap. What it can reach depends on what you're coming from — ask us and we'll tell you straight.

What happens to the email address I give you?

We store the address, the page you submitted it from, and the time. Nothing else — there's no account, no password and no profile behind it. The table only accepts inserts; the key this website uses cannot read the list back out. Ask us and we'll delete it, with no verification hoops.

Where does the data live?

A Supabase Postgres database in Sydney, Australia. That covers this site. The application at app.diurna.cc will handle your studio's data under a separate agreement, published when the product opens — we're not asking you to agree to something we haven't written yet.

Do I have to use the Claude part?

No. The MCP server is something you switch on if you want it. Diurna is a timesheet, an invoice and a profitability report without ever talking to a model, and nothing about the product assumes you will.

Waitlist

Diurna isn't open yet

We're finishing the multi-studio version. Leave your email and we'll tell you the day you can sign up — and what it costs, before anyone else.