How long does it take to deliver a custom system?

It depends on scope. A focused module, for example managing a field operation, usually takes 6 to 12 weeks from discovery to delivery. Larger systems are split into phases delivered separately.

How much does a custom project cost?

It varies with the scope and the complexity of the integrations. After the initial assessment, at no cost, we send you a fixed-price proposal per project, not an open hourly rate.

What if my process changes after delivery?

The system is documented and in your name. You can evolve it with us under the maintenance plan or with any other development team: there is no forced lock-in.

Can you connect to my ERP or to the plant’s PLCs?

Yes, as part of the scope. With the ERP we exchange catalogs, orders, or costs; with PLC, SCADA, or sensors we read what they already publish, without touching the control logic. Each integration is confirmed during discovery.

What if software that does this already exists?

We tell you. If a tool you already use, or one on the market, solves your problem better and for less, building it makes no sense. We propose a build when your process is specific enough that adapting generic software costs you more than it saves.

What do you need from me to make a proposal?

A conversation with the people who live the problem and, if you have them, the forms, sheets, and reports they use today. With that we come back with what we would build, in what order, and what stays out of phase one.

What technology do you build with?

We choose the technology per project, favoring open, widely supported standards, so the system isn’t tied to a single person or vendor.

With a conversation about your operation. From there comes an assessment and a solution proposal; you decide whether we continue.

Custom development

Software that fits your operation, not the other way around.

We are your development team for industry. We understand the problem holding your operation back, propose the solution, and build it around the way you work, integrated with what you already use and in your name.

We start from your problem, not a template
Integrated with what you already use
You own the code and the documentation

Tell us your problem Build your proposal

Your systemRequests · Approval flowSample view

Open requests

Plant and service sites · this week

Request	Stage	Owner
Valve replacement on steam line REQ-2148North Plant	Evidence	Supervision 2 h ago
Electrical panel expansion REQ-2146Shopping center	Request	Engineering 5 h ago
Warehouse lighting replacement REQ-2141Warehouse 3	Approval	Purchasing yesterday
Pump room inspection REQ-2137North Plant	Close	Closed Mon

Request

Stage

Valve replacement on steam line

REQ-2148North Plant

Evidence

Electrical panel expansion

REQ-2146Shopping center

Request

Warehouse lighting replacement

REQ-2141Warehouse 3

Approval

Pump room inspection

REQ-2137North Plant

ERPsynced 4 min agoEmail3 notices sent

This is for you if…

The conversation starts with your process, not with the technology.

First we understand the problem. Then we propose the solution.

In the first conversation we don’t show you a catalog: we listen to how you work today and tell you what we would build, what doesn’t need building, and why.

01
Your team forces a spreadsheet or a generic SaaS to do something it was never designed for.
02
You pay per-user licenses that go up every year for features half your team never uses.
03
You run a real process of your own —a plant, a service operation, a shopping center— that no generic software models well.
04
You want to own the system, not rent a subscription that can raise its price or disappear.

Problems we solve

Pick the one that looks like yours. We show you what we would propose to build and the first deliverable, so you can test it soon with your team.

Spreadsheets nobody consolidates

What happens today

Every site or shift fills in its own sheet. Someone merges them at month end, fixes broken formulas, and is never sure they have the latest version.

What we propose

A single entry point per site and a roll-up that builds itself

Web or mobile forms with your same fields and validations
A roll-up by site, area, and period, always current
Import of your historical sheets so you don’t start from zero

First deliverable

Your most-used sheet turned into a form, with its roll-up, to test at one site.

What changes: You stop chasing files by email: you see who submitted and who is missing.
Built with: Field appsOperations dashboards

Discuss this problem

Site entriesMonthly roll-upIllustrative example

October · 4 sites

Site	Records	Status
North Plant	31/31	Complete
Shopping center	31/31	Complete
Warehouse 3	28/31	3 missing
South Site	12/31	Behind

Last entry: Warehouse 3 · 12 min agoExport

Build your proposal

Check what hurts today and we show you what we would propose to build first. It is a starting point for the conversation, not a quote.

01What hurts today · Pick one or more

02Who will use it?

03What does it need to talk to? · Pick one or more

Your initial proposal: Phase 1: Field apps · +1 later

Your initial proposal

PHASE 1We propose starting with

Field apps

Forms, inspections, and evidence from the phone, with or without signal.

Forms and checklists with your fields
Photos, signatures, and location per record
Offline work that syncs when back online

Solves: Paper or spreadsheet forms from the field
Later: Operations dashboardsWhatever is not in the first delivery is written down, so nobody takes it for granted.
Platform: Web for the office and mobile for the field, on the same data.
Integrations: Connection to your ERP or accounting system: catalogs, orders, and costs without re-keying.
Size: Reference timelineIn phases: the first in 6 to 12 weeks, the rest delivered separately
First deliverable: Your most-used form in the app, to test on a real round or visit.
Where you start: A conversation about your operation and an assessment at no cost with the people who live the problem. With that, we send you a fixed-price proposal: what we build, in what order, and what stays out.

What we build

Six shapes a project usually takes, alone or combined. Open each one to see what it solves, what it includes, and how it could look.

What it solves: The “how is mine going?” emails and WhatsApp messages, and client approvals lost in the inbox.
What it includes
Per-client access to what each one can see
Requests with evidence, approval, and close
Downloadable documents and reports
Email notices on every stage change
Connects to
ERP
Email
Your order system
What it is not
An online store or a marketing site.
PortalMy requestsSample view
North Plant · 3 active requests
Valve replacement on steam line
REQ-2148
Waiting for your approval
Approve
Grounding system measurement
REQ-2139
In progress
Main panel review
REQ-2131
Closed
Visit report · REQ-2131.pdfWe email you on every change
What it solves: The “how is mine going?” emails and WhatsApp messages, and client approvals lost in the inbox.

PortalMy requestsSample view

North Plant · 3 active requests

Valve replacement on steam line
REQ-2148
Waiting for your approval
Approve
Grounding system measurement
REQ-2139
In progress
Main panel review
REQ-2131
Closed

Visit report · REQ-2131.pdf

What it includes

Per-client access to what each one can see
Requests with evidence, approval, and close
Downloadable documents and reports
Email notices on every stage change

Connects to

ERP
Email
Your order system

What it is not

An online store or a marketing site.

We don’t bend your operation to fit a catalog. We write the system your operation is already asking for, and hand it over so it is yours.

How a project comes together

Four stages and an evolution plan. Pick one to see what we do, what we need from you, and what you get when it closes.

Reference timeline

Weeks from kickoffMinimumUp to the maximumDepends on scope

Discovery

1–2 weeks

We learn how your operation works today, with the people who run it.

What we do

Interviews with real users
Map of the current process
Inventory of required integrations

What we need from you

Access to the people doing the work
Current forms, sheets, and reports

You get

Process map
Integration list
Preliminary scope

Before moving on: You agree on the scope of phase one.

When the project closes, you keep

01Assessment and architecture
Scope, data model, and technical architecture, reviewed with your team before any code is written.
02Working prototype
The critical screens, clickable, in the first few weeks.
03System in production
Full source code, version control, and deployment in your name.
04Technical documentation
Architecture and operations manuals another team can take over without depending on us.
05Training
Hands-on sessions with your administrators and operators before closing.
06Maintenance plan
Support, evolutionary, and corrective work, with scope and cost defined from the start.

How we work with you

What you can expect from us on any project, large or small.

01We tell you what not to build
If a well-built spreadsheet or a tool you already have solves the problem, we tell you. We only propose what is worth building.
02The code is yours
Source code, version control, and documentation are in your name. Stay with us or move to another team.
03Short deliveries you test
Every module lands in a test environment so you can review it with real data before we move to the next.
04No per-user licenses
You pay for the project and, if you want, a maintenance plan. Adding people to the system doesn’t charge you another seat.

The software unit of an engineering group

Adqueo is the software brand of Tecapa Electric. We build systems with the grain of plants, field crews, and compliance, because that is the world we work in.

Standards behind the method

ISO/IEC/IEEE 12207: Software life cycle processes: the source of our discovery, architecture, build, and delivery sequence.
ISO/IEC 25010: Software quality model: it guides the acceptance criteria of every delivery.
OWASP ASVS: Application security verification: authentication, access control, and data handling, before delivery.

Meet Tecapa Electric

Frequently asked questions

Is your case not here?

Tell us which problem you want to solve and we tell you how we would approach it. The first conversation has no cost.

Book a conversation

Tell us the problem. We propose the solution.