THE IDEA BEHIND MAYBIT
Global work.
A more local understanding of your money.
For an Indonesian freelancer, a payment arriving in USDC or USDT is the start of another workflow. Which client sent it? Which invoice does it settle? What should be set aside? What might be left in rupiah after conversion costs?
Maybit is being built to bring those questions into one workspace, using the wallets people already have.
Our focus: a read-only income workspace for Indonesian freelancers and remote professionals paid in stablecoins.
A focused first product
The working prototype brings together incoming transfers, client records, invoices, allocation plans, historical exchange-rate context, and estimated cash-out comparisons. The local prototype demonstrates that workflow with sample data.
Working in the prototype
Income records, client tagging, invoice matching, allocation planning, CSV reports, and a calculated Income Brief.
Still being validated
Live network indexing, exchange coverage and fees, payment reconciliation edge cases, and workflows with real users.
A useful role for Claude
The optional Income Brief integration sends a small, explicit set of aggregate figures to Claude for a plain-language explanation. The underlying arithmetic stays in application code. The user can inspect the source figures and return to their records.
Wallet addresses, transaction hashes, client names, email addresses, and notes are excluded from that request. An explanation requires consent. In the public demo, the brief is generated from sample records without calling an AI model.
The integration is implemented, but live model quality and cost still need evaluation. We're interested in measuring factual consistency, useful explanations, and the time it takes a freelancer to review their records.
Where we are today
Maybit is an early-stage, founder-led prototype. We have not yet validated demand through user interviews or established user traction. Our next step is to test the workflow with Indonesian freelancers and learn which parts of getting paid create the most avoidable admin.
What comes next
- Payment review: help users resolve ambiguous invoice matches.
- Income classification: distinguish client payments from transfers between a user's own wallets.
- Actual cash-out records: compare an estimate with what was really received.
- Reliable live data and a small, carefully evaluated beta.
Built around your control
Maybit does not hold funds, sign transactions, or execute conversions. Allocation plans are records, not transfers. Exchange comparisons are estimates, and income summaries are tools for reviewing records.