Your clients now live in one place. Add a client once in your Dekimu account, and every app you use sees the same entry — same name, same email, same notes, same history.
Before this, each app kept its own list. You'd type the same email into InvoiceUp that you'd already typed three times elsewhere. We built Dekimu so the tools feel like one business — not ten vendors with overlapping address books — and a unified client list was the next obvious step.
Open accounts.dekimu.com/clients. Create, rename, archive. Every app that asks for a client — InvoiceUp when you add an invoice, HelpMeNegotiate when you start a negotiation — reads from that single book. Pick the client from a dropdown. Done.
The account is the only place that writes client data. The apps read. That keeps the book in one shape, in one database, with one source of truth — and means a name change or a delete propagates everywhere in the same request.
The other half of the change: activity. When InvoiceUp sends a follow-up, when HelpMeNegotiate logs a counter-offer, both now post to the shared Recent Activity feed in your account. The security log you already had — sign-ins, password changes — stays on its tab. App events get their own tab. A third "All" tab shows everything in one stream.
A freelance business is one business. The tools should reflect that — the client book, the timeline, the login, all the same.
No email addresses anywhere in a Redis key name — every lookup is indexed by a hashed slice, so the identifiers themselves don't leak PII even to someone with database access. No emails in activity titles either; app events show the client's display name, not the raw address they emailed you from. The activity feed is capped per user and trimmed on every write.
What's next: clients will carry richer context over time — preferred cadence, payment history, negotiation notes — and every Dekimu app will be able to read that context without you re-entering it. The book is the anchor; the apps hang off it.