Collaborations
When time and budget are tight you need someone who knows what to build first and what can wait. I've worked with several startups and can follow the whole project: product, interface, code, servers.
I've collaborated with several startups and I know how it goes: shifting goals, limited cash, not enough time. I build the product in stages, so every release is already usable and can be tested with your first users.
If the idea calls for it I can add AI features (assistants, content search, automations) from the first release.
You don't need four suppliers who never talk to each other: from the first draft to going live you work with one person. My strength is code; interface, backend and hosting are complementary skills I cover as far as a solid MVP needs.
I turn the idea into simple flows and screens you can test. Enough for an MVP; for a full brand I work with a designer.
Vue, Nuxt and React: fast interfaces that suit every device and are ready to grow.
Databases, access control, payments and integrations with the services your product needs.
Test and production environments, automatic deploys, backups and monitoring.
From idea to a first live version
Quote
For products that evolve every week
Sprint rate
A technical presence, without hiring
Monthly hours
Learn more
Learn more
# Custom softwarecommit fe22ca4 ·
When an Excel sheet stops being a tool and becomes a risk: data integrity, permissions, concurrency, traceability. And how to design and migrate to a custom management system.
Read the article
# Mobile appscommit e7d859f ·
Native, cross-platform, web app or PWA: the real limits of PWAs on iOS, hardware access, distribution, maintenance costs and the technical criteria for deciding.
Read the article
# Software developmentcommit a5f2eae ·
A brief that produces reliable estimates: goals, functional and non-functional requirements, integrations, environments, code ownership and acceptance criteria. With a template.
Read the article
FAQ
It's the smallest version of the product that lets you test the idea with real users. We include only the essential features and postpone the rest: the first meeting is there to make that choice.
Read moreHow to write a brief for a developer: requirements, constraints and acceptance criteriaYes, when the product changes often it's the best way: short sprints, a shared backlog, a demo at the end of each sprint and priorities reviewed together. When the scope is already clear I prefer a fixed price.
It's measured in weeks, not months, but it depends on what's inside. After the first meeting you get a written estimate with milestones and timing.
Yes: we start from the feature that validates the idea, release early and add the rest as the first feedback or funding arrives.
You do: repositories, hosting and services are in your name and the code is documented, so a future CTO or another team can pick it up without depending on me.
I prepare the handover: documentation, repository rules and onboarding for new developers. If needed I can stay on as hourly support.