Eight problems we see again and again.
None of these cases are hypothetical: they're the situations that gave rise to our products. If you recognize yourself in one, we already know where to start — and if your case isn't here, it probably resembles one of them.
Condominium administrators and property managers
Nine condominiums, nine Excel files.
"I manage nine condominiums. Each one has its own Excel, its own account and its own way of collecting. To know how the month is going I have to open nine files and add them up by hand."
The symptoms
- A different file per community, with no real way to consolidate.
- Overdue payments are chased over WhatsApp, owner by owner.
- The monthly report for each board is built by hand, month after month.
- No one knows which units are current without opening the file and checking.
- If the person who keeps the books leaves, all the knowledge leaves with them.
- The DGII tax reports are prepared separately, by hand again.
How we solve it
- Global view: a dashboard with metrics for the whole portfolio — units, occupancy, income and total delinquency.
- Condominium switcher: you change community and every module reloads instantly.
- Delinquency ranking with progress bars and a comparison table across condominiums.
- Recurring charges: maintenance is generated automatically each month.
- Automatic monthly balance sent to owners without anyone building it.
- Guaranteed isolation: a guard checks on every request that the assignment is active. One community's data never touches another's.
- DGII 606, 607 and 608 exported in the official format.
| Before | After |
|---|---|
| Open nine files and add up by hand to close the month | One consolidated dashboard, updated in real time |
| Chase overdue payments over WhatsApp, one by one | Overdue units block themselves from bookings and voting |
| Build each board's report manually | Monthly balance sent automatically to owners |
| Knowledge lives in one person's head | Everything stays in the system, with history and audit |
HOA boards and single condominiums
The treasurer, their computer and a notebook.
"We're an HOA board. The treasurer keeps the books on their computer, residents call the office to find out what they owe, and hall bookings are written in a notebook."
The symptoms
- Residents call about everything: balance, receipt, visitor permit.
- Notebook bookings end with two families in the same hall.
- Votes require an in-person assembly and quorum never gathers.
- When the board changes, there's no history to hand over.
- Those who don't pay use the pool and gym just like everyone else.
- Security logs visits on paper, with no way to look it up later.
How we solve it
- Resident app: they see their balance, record the payment with proof and stop calling.
- Rule-based bookings: max per month, restricted hours, minimum notice and configurable approval per area.
- Digital voting with SHA-256 hash integrity, no duplicate votes, anonymous or identified.
- Automatic delinquency block: past the threshold, the unit loses bookings, amenities and voting.
- QR visitors generated from the app, with an entry/exit log.
- Announcements with read receipts: you know who saw them and who didn't.
| Before | After |
|---|---|
| "Call the office to find out what you owe" | The balance is on the phone, up to date |
| Notebook bookings, with clashes and arguments | A calendar with rules that prevent the conflict |
| In-person assembly that never reaches quorum | Auditable digital voting from the app |
| The new board starts from scratch | Full history, with an audit of every movement |
Companies required to invoice electronically
The DGII gave you a deadline and no one explained how.
"The DGII gave me a deadline to issue e-CF. My accountant talks about digital certificates and signed XML, and I just want to keep invoicing without my receipts being rejected."
The symptoms
- No one in the company knows what an XMLDSig signature or an XSD schema is.
- The receipt is rejected and you find out when it's already too late.
- Suppliers start sending their e-CF and you don't know what to do with them.
- The receipt types have different rules and get mixed up.
- The ITBIS summary for the filing is built by hand every month.
- If the internet goes down, invoicing stops.
How we solve it
- XSD validation before transmitting: if the XML doesn't comply, the send fails early and you see the error, not the DGII.
- Automatic Seed → token: the seed is signed and exchanged for the Bearer, with caching. You see none of that.
- All ten types from E31 to E47, each with its rules already implemented — including the E41 and E47 withholdings.
- Supplier intake: you record their XML, generate the acknowledgment (ARECF) and commercially approve or reject (ACECF).
- ITBIS summary generated for the filing, without rebuilding it.
- Contingency: receipts issued offline are transmitted later when the connection returns.
- Stamp and QR code on the PDF, and a job that checks status against the DGII periodically.
| Before | After |
|---|---|
| You learn of the rejection days later, from the accountant | The XML is validated against the XSD before it leaves |
| Supplier e-CF pile up unprocessed | Acknowledgment and commercial approval from the same screen |
| The ITBIS summary is built by hand every month | It generates itself, ready to file |
| No internet, no invoicing | Contingency: issue now, transmit later |
Companies with an ERP that already works
You don't want to ditch your system because of the DGII.
"I already have a billing system that works and took me years to tune. I'm not going to ditch it for the DGII, but I need to issue e-CF."
The symptoms
- Replacing the ERP is off the table: too much risk.
- The solutions offered mean double data entry.
- Your system has no way to know whether the receipt was accepted.
- No one documents the integration contract for you; you're left guessing.
How we solve it
- Public API with API Key: your ERP creates receipts and notes without anyone re-typing anything.
- Webhooks with retries: your system learns the result on its own, without polling in a loop. With an event catalog and delivery history.
- Status, PDF and XML lookup via API, to store them where you already do.
-
Swagger / OpenAPI and versioning (
api/v1/…): the contract is documented and doesn't break without warning. - Key rotation without cutting off the service.
- And if your ERP needs changes on its side, we make those too.
| Before | After |
|---|---|
| Invoice in your ERP and re-type it in another portal | Your ERP calls the API and the e-CF goes out on its own |
| No one knows if the DGII accepted the receipt | A webhook notifies your system of the result |
| Switch systems, with all the risk that entails | Your ERP stays; only the tax layer is added |
Sales and commercial teams
You know what they tell you on Mondays, not what happened.
"I have six reps out in the field. I know what they tell me in the Monday meeting, but I don't know what really happened on the visits or what was promised to whom."
The symptoms
- Visits are jotted in notebooks no one else reads.
- Quotes live in each rep's personal email.
- "I'll call you next week" and no one calls.
- The forecast is done on a hunch.
- A rep leaves and takes their book of business in their head.
- You quote, you close… and the invoice is paid late or not at all.
How we solve it
- Kanban pipeline: at a glance you see where each deal is stuck and since when.
- The visit creates the task automatically: you record purpose, outcome and next action, and the task is born with the priority and contact already set.
- Quote → invoice in an atomic transaction, with partial payments and outstanding balance.
- Three jobs every morning at 8:00: they flag overdue invoices, remind you of the day's follow-ups and alert on opportunities with no movement for more than 7 days.
- Forecast and lead funnel with data, not hunches.
- The book of business stays in the system: search by name, company or phone, with the full follow-up history.
| Before | After |
|---|---|
| The visit is jotted in a notebook and dies there | It's recorded and creates the follow-up task on its own |
| Monday meeting to find out about the pipeline | The Kanban is right there, updated, whenever you want to look |
| Overdue invoices no one notices | A job flags them every morning and notifies the owner |
| The rep leaves and takes the book of business | The book of business and its history stay in the company |
Human Resources departments
Physical folders and approvals by email.
"Each employee's file is a physical folder. To approve a promotion I send an email, which is answered with another email, and in three months no one can find who approved what."
The symptoms
- The record lives on paper, in a filing cabinet, in a single office.
- Approvals go through email, with no searchable trail.
- Recruitment is tracked in an Excel with a tab per vacancy.
- Payroll runs in another system that doesn't talk to the record.
- There's no formal org structure: the org chart is a PowerPoint.
- Loans and savings plans are tracked separately.
How we solve it
- Complete digital record: education, experience, references, dependents, emergency contacts and certifications.
- Personnel actions with approval flows that are traceable: promotions, rehires and disciplinary actions.
- Recruitment with requisitions and the full candidate lifecycle, including competencies, languages and health.
- Integrated payroll with loans, savings, cooperatives, bank accounts, withholdings and calendars.
- Real structure: departments, divisions, branches, cost centers, salary grades and occupational groups.
- Training and development: programs, courses and development plans per employee.
- Auditing in the database and in files, with Spanish and English support.
| Before | After |
|---|---|
| Dig through a physical folder to answer a question | The complete record, searchable in seconds |
| "Who approved this promotion?" — no one knows | The approval flow is recorded and audited |
| Payroll and record in systems that don't talk | One system, from candidate to paycheck |
| The org chart is an outdated PowerPoint | A living structure with cost centers and hierarchy |
Companies with a system no one can touch
The developer left and the server can't be turned off.
"Our system was built by a developer who's no longer here, it runs on a machine no one dares turn off, and every change we ask for is scary."
The symptoms
- A single server, with no backup anyone has tested restoring.
- No one understands the code and there's no documentation.
- It can't be updated: any change could bring the whole thing down.
- Years of data are in there, but there's no way to get it out.
- Shutting down operations to migrate is not an option.
How we solve it
- Understand first, touch later: we map the real process and the data model before writing a line.
- Phased modernization: the new system is stood up alongside the old one and both coexist until the replacement is complete.
- Data migration with prior validation: nothing is written without being reviewed first.
- Maintainable architecture: Clean Architecture, clear boundaries between modules and versioned migrations.
- CI/CD with Docker and GitHub Actions: deploying stops being a risky event and becomes routine.
- You keep the code and the documentation. The goal is for you not to depend on us, or on anyone.
| Before | After |
|---|---|
| Every change is a risky event | Continuous, reversible deployment, several times a week |
| A server no one dares turn off | Reproducible infrastructure with Docker |
| The knowledge left with whoever wrote it | Documented code another team can pick up |
Companies with data but no visibility
Five years of data and a forty-thousand-row Excel.
"My system has been full of data for five years. When I ask for a report, I get a forty-thousand-row Excel that no one reads."
The symptoms
- The reports exist, but no one opens them.
- Every question means asking someone to export something.
- Decisions are made on intuition, with the data sitting right there.
- Each department has its own version of the same figure.
- By the time the report arrives, it's already useless.
How we solve it
- Question first, chart later: we define what decision needs to be made and build backward from there.
- Dashboards by role: the manager and the operator don't need to see the same thing.
- Real-time KPIs with Power BI or built into your own system.
- A single source of truth: no more "my Excel says something else".
- Export when it's actually needed: to Excel, PDF or CSV, from the same dashboard.
- Alerts instead of reports: let the system tell you when something goes out of range, without you having to go look.
| Before | After |
|---|---|
| A 40-thousand-row Excel no one opens | A dashboard with the five figures that matter |
| Ask someone to export in order to answer a question | The answer is on screen, up to date |
| Each department with its own version of the figure | A single source of truth |
Your case isn't on this list?
Write to us anyway. In the first conversation we'll tell you frankly whether we can help — and if it's not our thing, we'll tell you that too.