Xwits Startups Sign in

Everything your studio runs on, in one place.

Clients, projects, hours, retainers and invoices. Built for software studios and agencies in India.

Sign in Ask for a demo Already have a studio code? Sign in.

Seven things a studio does every week — one place to do them.

You already know this month

Busy, and still short.

Everyone worked. The clients were happy. And the bank balance says otherwise.

Two invoices went out in March. Neither was chased. One is ninety days old.
Somebody spent three weeks on a fixed-price project that was quoted for one.
The retainer client was invoiced late again, because the person who remembers was on leave.
You will find out your billable share for the quarter in the second week of the next one.

None of these is a crisis on the day it happens. That is exactly why they compound — a studio does not fail at delivery, it fails at the twenty minutes a week nobody owns.

What you get

Seven jobs, one place.

StandupWhat is on fire, what is owed, who is stuck. One screen, every morning.
ClientsEvery enquiry, every client, every conversation in one history.
ProjectsA board per engagement. Tickets numbered so people can say them out loud.
TimeLog hours in one action. See who is busy and how much of it is billable.
RetainersThe monthly invoice raises itself on the day the contract says.
InvoicesGST-correct, numbered without gaps, payable by a link.
Your teamWho is here, who is on probation, and the letters each of them needs.

Your morning

One screen tells you whether to worry.

Three questions, answered before your coffee: is anything on fire, is the money coming in, is anybody stuck. On a good week it says nothing needs you.

One invoice is past its due date and nobody has chased it. Now
₹65.0kcommitted monthly
₹28.3kowed to you
71%team busy
18hunbilled

Why this one

Made for Indian businesses.

Rupees, not floatsEvery amount is exact. Nothing rounds, so your totals never drift.
GST that is correctCGST, SGST or IGST is worked out from your client's address. Nobody types it in.
Numbers with no gapsInvoice numbers run in order with no gaps, the way GST requires.
Your data is yoursNo other studio can see your records. Enforced by the database itself.

Where software should and should not be trusted

What runs on its own, and what waits for you.

Automation in a business you own is only worth having if you know exactly where it stops. So here is the line, drawn in the software rather than in a policy document.

Reversible things happen. Irreversible things wait. The gate is by class of action, not by named automation — so a feature added next year cannot slip past a rule by being new. Filing a CV against a role happens on its own. Replying to that candidate waits for you.
Nothing reaches a client unapproved The first message of any kind stops for a person. Approve it and that kind is yours; it does not quietly widen into something else you never agreed to.
A retainer bills once, provably Each period is claimed by a row with a unique key, so a job that runs twice — or retries after a crash — cannot invoice your client twice. That is a database guarantee, not a careful code path.
Backdated agreements do not fire back-invoices Record a retainer that began three months ago and it starts from the next billing day. Under-billing you can fix; a client charged for three months they already paid for by hand is a refund and a phone call.
Payments are reconciled, not assumed A webhook is a promise, not a guarantee. The system reads the provider's own list of payments back and finds what never arrived — and refuses to guess which invoice an unmatched payment belongs to, because a debt wrongly marked settled is never chased again.
Peer reviews cannot be swung by headcount Peers share a fixed slice rather than each holding a vote, so a rating does not move because somebody was on leave. And nobody learns who wrote what — below three replies the comments are withheld entirely, because two are guessable.
Utilisation says what it counted Measured against contracted hours, from approved time only, and the screen says so. Two figures that appear to disagree because one counts submitted hours and the other counts approved ones is how people stop believing a dashboard.
Your data is yours, structurally No other studio can reach your records. Enforced three times over, the last by the database itself. Where a model drafts text, GSTINs and PANs are stripped before the request and never restored.

There is no claim here about a proprietary algorithm, because the useful part is not the cleverness — it is that the arithmetic is written down, tested, and does the same thing on the last day of the quarter as it does today.