Business web applications
A company has outgrown spreadsheets, disconnected tools or a site that cannot support the real workflow.
For: Owners and operators who need software their team can actually use.
Includes
- Discovery of the current workflow, interface design in code and a working web application.
- Responsive screens, clear states and a handoff the team can maintain.
Does not include
- A fixed public price. Scope and cost are agreed in a proposal.
- Guaranteed revenue, traffic or certification.
A proposal after the workflow is understood, then working software in agreed milestones.
Request a proposal ↗Operations, orders and documents
Orders, approvals and documents live in different places, so the team cannot see one reliable state.
For: Distribution, commerce and service businesses with repetitive operational work.
Includes
- Product, customer and order flows, status filters and document history.
- Role-aware screens when the process needs them.
Does not include
- A claim of SAT certification or live fiscal filing beyond what a specific project has implemented.
- Publication of real customer, price or invoice data.
An anonymized example is the orders case. A new engagement starts from your process, not from that demo.
Request a proposal ↗Bookings, payments and integrations
Discovery, availability, payment and follow-up are separate conversations instead of one journey.
For: Tourism, appointments and other businesses that sell by reservation.
Includes
- Public catalog, reservation intent and integration with the services the process needs.
- Explicit payment state. Test mode stays labeled until live charges are intentionally enabled.
Does not include
- A promise of live payments, active users or revenue from Conecta. That product is still in development.
Conecta is the reference for this kind of system. A proposal defines what would be built for you.
Request a proposal ↗Process automation and practical AI
People repeat messages, checks and data entry that a clear workflow could carry.
For: Teams that already know the repetitive step and want it connected to their system.
Includes
- Form flows, API connections and conversational steps such as the WhatsApp and Dialogflow work described in the CV.
- A bounded assistant only where the source data and the failure state are clear.
Does not include
- An autonomous agent that replaces the business, or an AI feature with no reliable source.
The first delivery is the automated step and its visible states, not a vague AI promise.
Request a proposal ↗Specialist frontend engineering
A product team needs reliable React and Next.js capacity, from design to a maintainable interface.
For: Product teams, agencies and companies hiring for a defined frontend scope.
Includes
- Implementation, responsive behavior, accessible interaction and collaboration with an existing team.
Does not include
- A claim that every screen of a large platform was individually authored.
Salud Digna is the professional reference. Availability for employment is a conversation, not a start date.
Request a proposal ↗