An app in Kilango is a system you already work in. six are ready now, and the other forty-four are an offer: tell us which one you are missing, and we build it.
Connected, drawn and running in portals today. Open one to see what it shows and how it finds the data.
Projects, hours and the agreement frame.
Agreements, and their status.
Where the deal stands, and who has the ball.
Invoices, with what is outstanding and what is overdue.
The guides you have already written, where the question gets asked.
Documents, and only the ones the person may open.
The widgets are drawn and the app can be installed and placed. What is missing is the connection to the system itself, so the widgets show their empty state until it is wired.
Forty-four systems in eight categories that Kilango does not read yet. This is not a road map, and nothing here has a date on it.
We build it without charging for it. A connection we write once can be offered to the next customer who asks for it, so the work pays for itself. That is a better deal for us than a price list would be.
Write the system in the access request. If it has an API, it is usually days rather than weeks.
Then ask anyway. The list is the systems we have been asked about, not the ones we are able to read. If it has an API, it can be an app.
It works the same way, and it is often the fastest one, because you can answer the questions about it yourselves.