Less copied data. Work moving forward with clear rules.

When the same information moves from a form to a spreadsheet, from the spreadsheet to an email and from the email to another person, work is repeated at each handover. Lyntev analyses those stages and builds automations suited to your business’s tools and rules.

We can develop and support websites and systems entirely remotely, for clients in Portugal and other countries.

  1. An enquiry arrives

    A defined event starts the process.

  2. Rules and exceptions

    Each condition has a next step.

  3. A recorded action

    The team knows what happened.

The process is designed before the technology is chosen.

How much work could change in your process?

Use a representative month. Include the work that remains manual, review and follow-up. The scenario helps prepare the process assessment; validate the timings in a pilot.

Estimate working time

Compare current effort with a scenario including human review, tasks that remain manual and oversight. Initial values are a fictional example.

Monthly scenario data

Count occurrences of the same process in a representative month.

Team working time, excluding waiting.

Human work remaining in each automated task.

Remaining tasks retain their current time.

Maintenance and exceptions beyond the review already counted.

Time potentially freed: 8 h 20 min per month.

Current work
13 h 20 minPer month
Work in the scenario
5 hPer month

160 eligible tasks and 40 tasks retained in the current process.

How the calculation works

Eligible tasks = monthly tasks × eligible percentage ÷ 100.

Current work = monthly tasks × current minutes ÷ 60.

Work in the scenario = [(ineligible tasks × current minutes) + (eligible tasks × review minutes)] ÷ 60 + oversight hours.

The difference is current work minus work in the scenario. It may be negative. The calculation allows an average monthly volume, so the eligible quantity may be fractional.

Initial implementation effort is excluded. Time freed does not itself mean money saved: validate time and quality in a pilot.

Calculations run in this browser. Values are neither sent nor saved.

Example: from a website form to the CRM.

In an illustrative journey, the form receives the service, location and contact details. The CRM creates or updates the record, assigns a person responsible and prepares the notification. We define which identifier recognises the same contact and where the team checks the request’s status.

The test repeats the submission, leaves a required field blank and simulates the destination being unavailable. The expected outcome — update, request a correction or retain for intervention — is defined before activation. Scope depends on the tools chosen.

Start with a repetition you already know well.

A task with a known frequency, consistent inputs and understandable rules is a useful starting point. We describe the current journey, usual deviations and the information the team needs to consult.

The first project may resolve just one transfer between tools. Based on that result, you decide whether it is worth extending the flow to other teams or stages.

  • Organise requests received through forms.
  • Create and update customer records without manual duplication.
  • Route tasks according to service, status or person responsible.
  • Prepare notifications, reminders and documents from confirmed data.
  • Bring information together for periodic reports.

An existing integration may be enough.

We start by checking whether your CRM already offers a form or integration for the intended journey. If it covers the required fields, people responsible and rules, it may avoid additional development. When a custom connection is needed, we confirm how the programs allow data to be read and changed.

To assess the connection, specify the tools’ names and plans, the data source and destination, frequency and who may authorise access. The proposal separates configuration, development and ongoing costs. Submitting a form does not automatically include campaigns or messages through other channels.

A failure needs a known destination.

We define what happens if a program is unavailable, a field arrives blank or an operation is repeated. The flow should allow the problem to be recognised and work resumed without losing context or repeating an important action.

Approval points keep the team in control. It may be necessary to check a document, approve a change or validate a request before continuing. The level of automation is chosen for each stage according to the action’s effect.

When rules are enough and when AI helps.

If a request contains defined fields and the decision follows a clear condition, an automatic rule may resolve the task. When the task involves interpreting a message, locating information in a document or preparing a reply, AI can support one of the stages.

Interpretation and execution are assessed separately. An AI suggestion can be shown to the team for review before updating a record or sending a reply. If the process needs its own application, that part can form part of a bespoke system.

Which part of WhatsApp customer service do you want to automate?

Think about the last enquiry the team received after hours. If saying when you reopen was enough, configure the away message in the WhatsApp Business app. If someone asked about a service, identify who keeps prices and opening hours updated and who replies when information is missing.

If work continues after the reply, follow a fictional request through to the end. For example, a garage receives a question about a service, asks for missing information and prepares a quote. Compare where the conversation stays, who takes responsibility for the request and how the team finds quotes still awaiting a reply.

How many months does it take to recover an automation investment?

Before the pilot, choose a simple measure: time to handle a request, tasks requiring correction or duplicate records. Note the volume and conditions so you can compare the same task after implementation.

The test result guides further development. We adjust exceptions, instructions and responsibilities before increasing scope. Tool usage costs also form part of that assessment.

Fictional calculation example for a company paying overtime. A pilot costs 600 € to implement and 30 € per month to operate. If the company verifies that it no longer pays 90 € in overtime each month, the net saving is 60 € and implementation pays back in ten months. Replace these figures with the costs in your proposal.

If the team has only freed up time for other enquiries, record those hours as available capacity. To calculate a payback period in euros, you need an expense actually avoided or measured additional margin. With a monthly benefit equal to or lower than operating cost, the initial investment remains unrecovered.

Choose your starting point.

Process assessment

400 €

We study your process and deliver the system design, timescales and a fixed price.

  • Mapping of the current process
  • A proposal for features and phases
  • A fixed price and schedule
Request a process assessment

Bespoke software

400 € per day

Appointment calendars, CRM, client portals, quotes, stock management or AI automations.

  • A fixed price for each phase before work starts
  • A preview at each phase
  • Exportable code and data
Request a quote

Integrations and external service costs are identified in the proposal. The process assessment fee is deducted from the project if you proceed. View prices and what is included.

Total amounts payable, exempt from VAT under Article 53 of the Portuguese VAT Code (CIVA).

We also build our own systems.

If an existing product covers your process, it can be your starting point. These are Lyntev solutions with published features and terms.

ContactoIA

The AI answers using information from your business. You can organise enquiries, contacts and opportunities on a board with stages (Kanban CRM). Follow each conversation.

Discover ContactoIA

BeautyFlow IA

A simple system built for beauty salons. It brings together calendars for each professional, online booking, clients, packages and finances.

Discover BeautyFlow

Clínicas Pro

Organise appointments, follow up with patients and see what is due to be received. Each team member accesses the tools they need.

Discover Clínicas Pro

How we work with you.

  1. Map a repetition

    We identify the input, stages, people involved, tools and expected outcome.

  2. Confirm connections and rules

    We check access, limits, required data, recurring costs and exceptions along the journey.

  3. Test a limited flow

    We use prepared cases, including failures and repetitions, before putting the process into use.

  4. Measure and continue

    We check the result and document how to monitor, correct and develop the automation.

Before you proceed.

Is artificial intelligence necessary?

Not at every stage. Clear rules and structured data can be handled by conventional automation. AI is assessed when a task requires interpretation, such as classifying free text or preparing a summary. The project may combine both types of stage.

Can you automate the process without replacing the programs?

It is a possibility we analyse first. It depends on the current programs’ integrations and access. The proposal explains what stays, what connection will be built and whether any part needs an alternative.

What happens if the automation fails?

Failure handling is defined in the project: how to identify the problem, which tasks remain pending and who intervenes. Actions needing checking can await approval. We test the agreed cases before expanding use.

How much does an automation cost?

The price depends on the number of stages, connections and exception handling. For bespoke projects, the published diagnostic assessment is 400 €, deducted if you proceed, and development has a reference rate of 400 € per day, with a fixed price per stage. Third-party costs are identified separately.

Can you connect forms, CRM and emails?

That is a type of journey we can study. We confirm fields, contact statuses, the sending service and available access. Messages and sending rules are defined within the project scope.

Can we start with a small process?

Yes. A frequent transfer with a clear input and outcome lets you test operation and monitoring. After measuring the pilot, you can decide whether to add other stages.