Custom software · Service businesses

Software for requests and documents.

Customer portals, case files and approval workflows. We define one process with you, build the application and connect it to the agreed systems.

Direct access to your development team. Spain and Latin America.

KENEA / WORKFLOW01—03
01
INPUTA request arrives.

Customer, context and documents.

02
APPLICATION + AIThe team reviews it.

Required data, source and owner.

03
CONNECTED SYSTEMSThe next step is recorded.

Status, history and connected tools.

Illustrative workflow

Choose a starting point

One defined process to start with.

Requests, case files or documents with AI. Explore a workflow before outlining your own.

Requests and approvals

Assign requests, collect documents and record who authorises the next step.

An example for property managers and service teams where several people handle a request.

Discuss this type of project
Atlas / RequestsExample

Requests

Today
Received04
Awaiting approval02
Request 024Documentation received
Review
Request 023Owner assigned
In progress
Review request

Source document · History · Next step

Customer portal

Collect documents and show each case’s progress in a private space with permissions.

An example for professional services coordinating customers and their internal team.

Discuss this type of project
Atlas / Case filesExample

Case files

Today
Open04
For review02
Request 024Documentation received
Review
Request 023Owner assigned
In progress
Review case

Source document · History · Next step

Document AI

Prepare an extraction or summary and check it against the original document.

The source and human review are part of the workflow before the result is approved.

Discuss this type of project
Atlas / Document reviewExample

Document review

Today
Received04
For review02
Request 024Documentation received
Review
Request 023Owner assigned
In progress
Check source

Source document · History · Next step

Illustrations with fictional data. A real project requires development, connected systems and agreed tests.

Define a useful first release

A first process, with scope and tests.

We review users, documents and systems before proposing development. You receive a proposal with scope, timing, price and acceptance criteria.

  1. 01

    Screens and permissions

    Who uses the application, what they can do and which information they can access.

  2. 02

    Development and connections

    Working software, agreed integrations and treatment of errors and duplicate data.

  3. 03

    Testing and handover

    A reviewable version, deployment, documentation and agreed access to the code.

We can also take on a defined module or integration within an agency project. Hosting, AI usage and maintenance are agreed separately.

Tell us about the project

A short description is enough. You do not need a finished specification.

What needs to change, who will use it and any deadlines you are working towards.

Add technical contextOptional

For example: a website, Microsoft 365, a CRM or custom software

Do not include passwords, confidential documents or personal data about other people.

Sending an enquiry does not commit you to a service.

Kenea / Your privacy

Only what is needed.

Kenea does not use advertising trackers. The assessment works without identification and only sends data if you decide to contact us.

Technical preference
Stored for six months only if you choose to save it.
Colour theme
Your explicit light or dark choice is kept in this browser.
Assessment
Answers remain in the page until you choose to send them.