NIKAPROJECTView full project
nika.
An AI assistant
for customer support.
A platform connecting AI agents, business context and customer conversations.
SENIOR DEVELOPER & AI SPECIALIST
Software made
for your business.
I build tools to organize processes, automate tasks and connect the systems your company already uses. I also develop artificial intelligence assistants.
SELECTED WORKProducts I designed.
Products I designed.
Systems I developed.
Nika, CarameloVet and Fomenta show my work across product, interface, full-stack development, automation and artificial intelligence.
An AI assistant
CARAMELOVETPROJECTView full project
CarameloVet.
Veterinary care
connected end to end.
A telemedicine platform for pet owners, veterinarians and operations. In development.
FOMENTAPROJECTView full project
Fomenta.
Ideas organized
through a clearer journey.
A platform for innovation programs with guided applications, learning and an AI copilot.
WHAT I BUILDSystem development.
System development.
Automation and AI.
I can build a new tool, connect the systems you already use or improve an application you already have.
HOW I WORKFrom what you need
From what you need
to a system in use.
First I understand how the work is done today. Then we define what will be built. During development you follow each delivery and validate the adjustments.
- Understand
Understand the work and where it hurts.
We talk about who will use the solution, which tools already exist and where the delays and manual steps are. That is how we set the priorities.
Problem and priorities defined - Decide
Define what goes into the project.
I assess what can be reused and what has to be built. We agree on features, integrations, timeline and budget before starting.
Scope, timeline and budget agreed - Build and test
Build, test and put to use.
I develop in stages and test the planned flows with you. We adjust what is needed within the scope and prepare the release and the access.
Delivered as agreed in the scope
What to know before hiring.
From defining the scope to what happens after launch.
Do I need a complete specification?
No. Start by telling me what you need to solve, who will use the solution and how the work is done today.
With that context, we can organize priorities and agree on what needs to be part of the first release.
Does my current system need a rebuild?
Not necessarily. I first assess the existing system: what works, where its limitations are and what can be reused.
The solution may be fixing a workflow, connecting tools or adding features. A rebuild only makes sense when there is a technical reason for it.
How do you estimate cost and timing?
From the scope: features, integrations, the condition of the current system and external dependencies. These details make it possible to estimate the work.
The proposal sets out what is included, the timeline and what can wait for a later phase. Scope changes need a new agreement.
What happens after the system goes live?
Launch and maintenance are different stages. We need to agree on who manages hosting, access and integrations, and how fixes and new features will be handled.
The terms for corrections, support and further development should be clear in the proposal, without assuming ongoing support is included.
Let’s talk.
Start with the problem.
You do not need a finished scope. Tell me what you want to build, improve or automate and give me enough context to understand the situation.
Prefer to write directly?