Say you run a small shop. Clients, jobs that need doing, invoices that need chasing, and a head that is already full.
Most people in that position end up with a pile. A spreadsheet for jobs. Notes for client quirks. A todo list that is actually a graveyard. Something else for who owes what. Email for everything that did not fit.
Thogits is one place for that pile. Records you own, pages the AI builds against those records, and an assistant that can chat, email, or call — and write the result back. Short version of the product: What is Thogits.
This is a walkthrough of one system, not a customer story. Names below are examples.
The system
You need five things to run the week:
- Clients
- Jobs (or tickets — same idea)
- Invoices (who owes what)
- Follow-ups
- One dashboard you can open on Monday morning
The database holds typed records. A client is a client. A job is a job. An invoice is an invoice. Pages sit on top of those records — screens, not a document with a table glued in.
If you already think in tickets, start from tickets. More people than jobs: CRM. Money is the pain: invoices. Same product. Different starting shape. You can install a template and then change it.
Records that persist
A client walks in, emails, or calls. You capture them once.
Say a regular wants a fridge repaired on Thursday. That is a job linked to that client — status, due date, notes about the model. When the job is done, you mark it done. If they owe you, you add an invoice record pointing at the same client and job.
Voice or email in, records persist. That is the loop.
Tell the assistant in chat: “New job for Priya, leak under the sink, Friday afternoon.” Email it. Call it. The record is there after, on the web and on iPhone. Live sync — not an offline copy you merge later.
The assistant can create and update records, and it can build the pages you work in. An agent you already have can see and edit the same records over MCP. MCP does not build pages. The split is in Bring your own agent.
Invoices, honestly
None of this is a billing product. Thogits is not Xero and it is not Stripe. The invoice tracker is who owes what, how much, and whether you have chased them. You still send money and file tax however you already do. You stop losing the thread of who has not paid.
One dashboard
Ask for a page.
“Give me a dashboard: jobs due this week, invoices still open, clients I have not spoken to in 30 days.”
The AI builds a real screen on those records. Not a mock. Not a canned view you click through until it looks close. You open it. You work in it. When Friday’s jobs close, the dashboard is already looking at next week.
If you want last week’s finished tickets as their own screen, ask for that too. How that differs from mockup generators is in Pages the AI actually builds.
You are running a system — tickets, people, money. The screen sits on the database.
Follow-ups without memory
The job is not done when the work is done. Someone has to chase the unpaid invoice, confirm Tuesday, remember the client who said “call me in a month.”
You can set a reminder. You can schedule an automation to remind you, wake the assistant, or run a script. Automations are schedule-based. They fire at a time. They do not watch every field and fire “when a record changes.”
Every Monday at 8, who still owes. That is what the schedule is for.
The assistant can also do the follow-up — chat, email, or a phone call — and update the record as it goes.
A week, not a launch
Monday. You open the dashboard. Three jobs, two invoices still open, one client you have been meaning to ring. You call the assistant, or you call the client and tell the assistant afterwards. The note lands on the record.
Tuesday. A new job arrives by email. The assistant creates it, tagged to the right client. You do not retype it into a sheet.
Wednesday. You finish two jobs and ask for a page of this week’s finished work. A screen on those records, not a report you print and lose.
Thursday. You add two invoice records — who, how much, linked to the jobs — and set a reminder for next week if they have not paid.
Friday. Your coworker is covering the afternoon. You invite them. Same jobs, invoices, dashboard. The people doing the work share the space. You are not maintaining a permission tree so the wiki can pretend to be a company.
Sync is web and iOS. Counter or van. Same records. There is no offline mode to babysit.
What you are not buying
Not a billing stack: track who owes what; charge people however you already do. Not a helpdesk with SLAs: tickets here are jobs you run. Not a docs wiki: you can keep notes and docs next to the work, but the system of record is the database.
Not a giant template library. Shape the workspace: projects if the work is longer than a ticket, a directory if the people graph is the thing, todos if the list is personal-scale. Personal and teams are the same idea at different sizes.
And not a mock. Pages compile against your data. The assistant writes to the same data. MCP writes to the same data.
Start with the work, not the category
If “I need a CRM” is already true, start there. If it is “stop losing jobs,” start with tickets. If it is “I never know who has paid,” start with invoices. Then add the rest.
Clients, jobs, invoices, follow-ups, one dashboard. Voice or email in. Records persist. Coworkers invited. Phone and web in sync.
Pricing is per workspace, not per seat. Free is enough to try the loop. The pile is optional. The system is just one place.