← Back to all posts

Your app now writes its own invoices, contracts and reports

Your app now writes its own invoices, contracts and reports

Every business app eventually needs to hand someone a document. An invoice for a customer. A quote to approve. A delivery note to sign at the door. A monthly report for the accountant. A contract with two signatures on it.

Kreova apps can now do all of that on their own. You describe the document in plain English, and the app produces it on demand, filled with the data as it is right now.

One saved document, every format

When you ask for an invoice, the agent designs it once: your letterhead and logo, the customer's details, the line items with their totals, your bank details, a QR code, signature lines. From that one design, your app can hand out:

  • PDF, crisp and ready to print or send
  • Word, for anyone who wants to edit it
  • Excel, with numbers that stay numbers and totals that are real formulas, so your accountant can work with them
  • PowerPoint, for when a quote needs to be presented
  • CSV, Markdown, plain text and JSON, for bookkeeping tools and anything else that reads data

And because the design is saved, not baked into a page, changing it changes every document from then on. Tell the agent "change the heading to Tax Invoice and add the PO reference under the date", and the very next download has it. No rebuild.

Fast enough that nobody waits

Routine documents are generated directly from your data, without opening a browser behind the scenes. On a real invoice we measured it at 176 milliseconds. Printing the same invoice from a web page took 1,147. That's more than six times faster, and the file came out at a quarter of the size.

When you do want a page printed exactly as it looks, like a designed price list or a brochure, the app does that too. Ask for "a PDF that looks exactly like the page" and that's what you get.

Download, email or zip

The same document works everywhere your app needs it:

  • A download button on any record: one click, the file.
  • An email attachment: mark an invoice Sent and the customer gets it with the PDF attached, and you get a copy.
  • A zip of many: every invoice from this month, in one file, each one named properly.

Signatures and contracts

Documents can carry signature lines: blank lines for signing by hand, or a real signature. In one test we asked for a service agreement that customers sign in their portal. The customer draws their signature on screen, and the signed PDF, with their signature, name and the date in the workshop's own timezone, is emailed to both sides the moment they sign.

Safe by default

A document is only ever generated with the permissions of the person asking for it. A customer can download their own invoice and nobody else's. If a document would need information someone isn't allowed to see, it isn't produced at all, rather than coming out with a gap in it.

It also won't send something broken. If an invoice is missing something it needs, like the customer's name or a due date, the app refuses to generate it and names what's missing, rather than emailing a customer an invoice with a hole in it.

It knows when to ask

When we asked for a public price list, the agent built the page and then stopped to ask for the real prices instead of inventing some. In its words:

"Your services or products and their prices are not something I can invent (a fake "$450" next to a real product would just be a lie on your public site)."

That's the kind of judgement you want behind a document that goes out with your name on it.

Try it

Open any project and ask for what you need: "give me a PDF invoice with my logo and bank details", "let staff download this month's invoices as a zip", "add a contract customers can sign in their portal". The rest is built for you.