Quote.
Send.
Close.

The local-first version is designed so you can start without a mandatory login. Your main configuration can be stored directly on your device.

Business name, logo, currency, basic business information, and, if you want, your payment method or external payment link. That information is reused on future jobs so you do not have to enter it again.

No. In the full version, you set up your logo once and it stays associated with your business on that device.

Yes. It is designed as a PWA so you can install it on a phone, tablet, or computer and open it like a regular app.

Much of the local experience, such as creating, editing, viewing history, and rendering documents, can work offline. Sharing on WhatsApp, using AI features, or accessing external services requires a connection.

With the local-first architecture, core information can be stored in IndexedDB inside your browser or PWA installation. Every operation does not need to travel to a server.

The product philosophy is to keep as much processing local as possible. Features that require external services, such as online AI, will be clearly identified so you know when something leaves the device.

If you clear site data, uninstall the PWA in certain ways, or clear browser storage, you could remove locally stored information. That is why Clousit includes clear export and backup tools.

Selling client or job data is not part of the product model. Clousit is a software product, not a business built around selling your information.

Yes. The landing demo may limit the number to keep it fast, but the full product is designed to support all the services a job needs.

Yes. You can change it only for that job or update the saved price for future quotes.

They are services, prices, and combinations that Clousit recognizes as frequent. Instead of typing the same thing every time, you can tap them and add them quickly.

No. Final prices belong to the business. Clousit can remember, suggest, or flag differences, but the user confirms what gets sent.

Yes. Quotes can include notes, scope of work, validity, terms, and other fields needed to present the deal clearly.

The architecture supports optional photos, especially for visual templates such as before/after, project showcase, or jobs where images help sell the service.

Yes. The idea is to reuse the same client, services, amounts, and branding without typing everything again.

Yes. Clousit can record how much was received, calculate the outstanding balance, and generate an updated document with the appropriate status.

They are visual job statuses. The final document can include a stamp or indicator showing how much was paid and how much remains due.

In the first version, any “invoice” should be understood as a commercial/non-tax document. Tax invoicing depends on each country’s rules and would require specific integrations.

The roadmap includes OCR to detect basic information such as total, date, or merchant and apply an expense or credit to the job after the user confirms the detected information.

Not for the basic flow. Clousit generates the visual document and uses the device’s sharing options or compatible links. You decide where to send it.

Clousit primarily generates a visually strong image for WhatsApp, while also offering download or PDF when it makes sense.

Yes. You can save it locally and organize it however you prefer.

Yes. Whenever the device and browser allow it, the document can be shared through the Share Sheet or downloaded for use in any channel.

No. Clousit is designed to offer different visual compositions. Templates should not be limited to changing colors: they can change hierarchy, structure, photos, cards, blocks, and overall style.

Yes. You can choose the style that best represents the business or type of job.

Basic templates offer clean, professional presentations. Pro templates can use more advanced compositions, integrated photography, higher-impact hierarchy, industry-specific layouts, and a presentation closer to a premium commercial proposal.

The goal is for templates to adapt to the user’s branding so the document feels like their own rather than a generic template.

DOTi is Clousit’s intelligent layer. It can guide the workflow, explain options, detect errors, and help turn messy information into something usable.

No. DOTi helps, suggests, and organizes. The user still controls prices, scope, documents, and final actions.

On the AI plan, the goal is to allow natural language and voice to turn a description into services, quantities, and prices ready for review.

Yes. That is why Clousit should show the information for review before sending. AI speeds up the work, but it does not remove the responsibility to confirm amounts and terms.

Not in the first version. The business can keep charging the way it already does today: cash, bank transfer, card terminal, PayPal, Mercado Pago, Stripe, or another provider.

Yes. Settings can store your own payment link or QR code so you can include it in quotes whenever you want.

Not in the initial model. If payment integrations are added in the future, sensitive data should be handled by specialized providers.

If you use an external provider, any decline, refund, chargeback, or banking issue is handled directly with that provider.

Not necessarily. In a local-first architecture without a cloud account, each device has its own storage.

Clousit should provide backup export and import so you can move your settings and history whenever you need to.

If everything is stored only locally and there is no backup, you can also lose that data. That is why exporting backups periodically is important.

A future version may include sync or a backend if the product and users justify it, but the initial goal is to keep Clousit simple, fast, and manageable.