Midday is gone.
Here's where Worklyn is going.

What Midday got right

Midday understood something that most freelancer software still misses. Invoices, transactions, receipts, time and financial context are not separate administrative jobs. They are different records describing the same business.

Its product brought invoicing, transactions, time tracking, customers, files and receipt matching into one connected system. Midday's founders later joined Ramp, with the standalone product entering a wind-down period.

That mattered because people were not only losing an invoicing tool. They were losing the place where a meaningful part of their business history lived. And that made me look differently at what Worklyn was becoming.

Worklyn was already connecting the work

The original problem behind Worklyn was operational. A client lived in one place. The proposal lived somewhere else. The contract was a PDF. The project was in another app. Time was tracked separately. The invoice came later.

So Worklyn began by connecting those stages, from client through proposal and contract to project and invoice. That was already useful. But it was incomplete, because sending the invoice is not where the business story ends.

The missing half was the financial outcome

Consider a project that looks perfectly healthy. The tasks are done. The client is happy. The invoice has been sent. From a project-management perspective, the job is finished.

But financially?

• Maybe only 60% of the invoice has actually been collected.
• Maybe the project consumed twice as many hours as expected.
• Maybe a contractor cost €1,800.
• Maybe three expenses were never attached to the project.
• Maybe the payment is sitting in the bank without anyone connecting it to the invoice.

Suddenly the same project tells a very different story.

Transactions are becoming first-class records

A transaction should not be a line imported from your bank and forgotten. It is evidence that something actually happened. Someone paid you. You bought something. A subscription renewed. A contractor was paid. A refund arrived. But the transaction alone does not explain any of that.

Worklyn's job is to connect the movement of money to the business record behind it. For money coming in, that runs transaction to payment to invoice to project to client. For money going out, transaction to expense to project, and where there is supporting documentation, receipt to transaction to expense to project.

Worklyn's current transaction workflow already supports matching incoming deposits to open invoices and outgoing transactions to financial documents, with confirmation before reconciliation. The important part is not the feed. It is the connection.

Reconciliation closes the loop

There is a subtle but important difference between “this looks like the payment” and “this is the payment”. Worklyn can suggest relationships. You confirm them. Then the records become part of the same financial story.

That principle matters because financial software should help without quietly inventing certainty. Matching can be automated. Reconciliation should mean the relationship has actually been confirmed.

And once it is, the rest of the workspace should understand the consequence. The invoice is paid. The outstanding amount changes. The project financials update. The transaction no longer needs attention. One action should finish the record everywhere it matters.

Receipts should explain money that already moved

Receipts have traditionally been treated as files you save because your accountant might ask for them later. That is backwards. A receipt explains a financial event that has already happened.

Worklyn's inbox reads the document, extracts the relevant details and looks through transaction history for a likely match. You confirm the relationship before anything is attached. Once connected, the receipt is not just a file: it explains the transaction, the transaction explains the cost, and the cost can explain what happened to a project's margin.

The project is becoming the financial unit of the work

A business-wide P&L is useful. But if you run client work, one of the most useful questions is much smaller: was this project actually worth doing?

Worklyn already brings the budget, tracked time, project expenses, invoiced amounts, collected payments, outstanding amounts and margin into the same project. That changes the purpose of the project page. It is not only where you ask whether you are on schedule. It is also where you ask whether you are still making money.

A project can be beautifully delivered and commercially terrible. I want Worklyn to show that while there is still time to do something about it. Not three weeks later in a spreadsheet.

Worklyn is not becoming accounting software

This part is important. We are not building a general ledger. We are not replacing your accountant. We are not trying to file your taxes. We are not trying to recreate QuickBooks or Xero inside a project-management app.

There is an important layer between running a business and doing the accounting, and that layer is where Worklyn belongs. The invoice has been issued. The payment has arrived. The transaction has been categorized. The receipt has been attached. The relationship has been reconciled. The project context is known. Now the records are ready to move downstream. That is pre-accounting.

Month-end should be a review, not an investigation

I do not want the end of the month to begin with:

• What was this €392 transaction?
• Where is the receipt for this?
• Did that client ever pay?
• Which project did this contractor work on?
• Why does the bank say one thing and the invoice list say another?

Those questions should be answered while the business runs. Then month-end becomes much less dramatic: review what is incomplete, fix the few records that need attention, export or sync them, move on.

That is a much better role for pre-accounting software than trying to turn every independent professional into their own accountant.

AI only gets interesting after the context exists

There is an obvious temptation to put AI at the center of every software product right now. I do not think that is the interesting part. An AI assistant with disconnected data is still working with disconnected data.

The more important work is underneath it. The project knows the client. The invoice knows the project. The payment knows the invoice. The receipt knows the transaction. The transaction knows the project cost.

Once those relationships exist, asking questions becomes much more useful. Which projects are losing margin? What is still waiting to be paid? What is keeping this month from being ready for accounting? What should I pay attention to this week?

AI should reason over the business. It should not be the thing holding the business together.

What is not changing

Worklyn is still a product for running the business. Clients are not disappearing behind finance dashboards. Projects are not becoming accounting dimensions. Proposals and contracts are not becoming bookkeeping records.

The work still comes first. Finance is becoming the layer that follows it. That distinction matters. I do not want to build accounting software with a project-management tab. I want to build a business workspace where the financial outcome of the work is impossible to lose.

Midday did not give Worklyn this idea. It sharpened it.

I was already building toward a product where the operational and financial sides of a business belonged together. But Midday's shutdown forced me to look at the priority differently.

A product that manages the client, proposal, contract and project but treats the financial outcome as something downstream is still leaving the owner to connect the final pieces themselves. That no longer feels good enough.

So finance moved from something Worklyn should also understand, to one of the things Worklyn is fundamentally built around. That is the change.

Your business should not have to be reconstructed from its software

A client is not a CRM row. A project is not a Kanban board. An invoice is not revenue. A payment is not just a bank transaction. A receipt is not just a PDF. They are pieces of the same story.

Software separated them because separate tools were easier to build. The business itself was never separated that way. Neither should Worklyn be.