Digital solutions to sell and work better.

No. Tell me what you want to achieve, who would use it and how you handle it today. We can use that to sort priorities, identify constraints and define a useful first version. A conversation, an example or a few notes can be enough to start understanding the problem.

I don't limit my work to one industry. I want to understand the process, the people involved and the outcome you need. Then we can assess whether a website, an internal tool, an automation or an application is appropriate, and whether my approach fits your needs.

Yes, we can start with what exists. First, we review what works, where the difficulties are and what access or documentation is available. That helps us decide what to keep, what to adjust and whether anything needs rebuilding before we agree on the scope.

They depend on scope, integrations and the material available. First, we clarify deliverables, priorities and dependencies; then we agree on a proposal with clear milestones and boundaries. If a new need comes up, we review its impact on time and budget before including it.

Work moves through stages you can review: a structure, a design or a working version, depending on the stage. We compare each delivery with the agreed goal and gather your feedback. This helps us adjust course and distinguish a correction from an extension of the project.

We can assess connections with forms, email, a CRM, spreadsheets or other systems. Feasibility depends on their APIs, permissions and limits. Before proposing an integration, we review which information needs to move, who can access it and what should happen if something fails.

Only if it offers a concrete improvement, such as classifying requests, extracting information or preparing a response for review. A conventional automation may be enough. If we use AI, we define its limits, the data it needs and the steps that require human validation.

If you need to publish or edit frequently, we can include a CMS or an administration panel. We define which content you can change, the permissions required and how to use it. That capability is part of the agreed scope; Aurora demonstrates this kind of tool.

We define the handoff from the start: code, access, documentation and launch support according to the scope. We also clarify how to operate what we've built. Hosting, licences, external service usage and any ongoing maintenance are detailed in the proposal so you know what is covered.

They are my own projects for exploring interfaces and complete flows. Each case explains what works, which data is illustrative and what is simulated. They help us discuss possibilities and show how I work; your project is defined around its context, users and requirements.