Most collaborations start with one specific thing to move forward, then grow naturally if the fit is good.
Start with something clear: a website, a landing page, a frontend task or a fix. If the fit is good, I can stay close as a technical partner.
Most collaborations start with one specific thing to move forward, then grow naturally if the fit is good.
A page, a website, a fix, a launch or a technical problem that needs calm, practical execution.
I work inside your existing flow, keep tasks readable and flag technical decisions early.
A good fit for agencies with design, strategy and client relationships already in place, who need dependable development support without adding noise to the project.
Most collaborations begin with one clear task that needs to move forward.
On WordPress projects, this often includes custom WordPress websites and flexible fields, page sections and editor-friendly content structures.
After the first task, I can support the agency across updates, launches, maintenance and daily technical work.
Useful when you need extra technical capacity without adding another layer of management.
Once there is trust and context, I can help with integrations, workflows, internal tools and practical technical decisions.
Support for the technical pieces that sit around the website or product.
I’m used to working asynchronously with agencies and small teams. The goal is simple: keep priorities visible, communication clear, progress easy to follow and decisions easy to trace.
I usually work with a lightweight Kanban board for tasks, priorities and status.
Quick questions, daily context and project decisions can stay in the channel your team already uses.
Briefs, assets, specs and decisions are kept in shared documents so the project does not depend on memory.
I keep updates short, surface blockers early and avoid turning every decision into a meeting.
Flexible on tools. I adapt to your setup, or help shape a simple one that people actually use.
15+ years of full stack development across a few stacks I know well. The goal is not to use every tool, but to choose the right level of complexity for the work.
WordPress development, WooCommerce work and flexible fields, page sections and editor-friendly content structures with Advanced Custom Fields for sites that need to be easy for teams and clients to update.
Dashboards, internal tools and PHP applications with Livewire and Alpine.js when the UI needs to stay practical, reactive and maintainable.
SaaS products, MVPs and admin platforms with Hotwire and Stimulus when server-rendered interfaces need to stay fast without unnecessary frontend complexity.
Clean implementation from design to working interface, plus databases, API integrations, hosting and deployment when the project needs the full path to go live.
* I can help with design too when useful, especially layout, UX details and practical visual decisions. Most projects still start from an existing design, brand or agency direction.
A few practical answers for agencies that are considering bringing me into a project or a longer collaboration.
No. WordPress is often the starting point, especially for agencies that need custom websites, editor-friendly pages or flexible content with ACF. I can also help with frontend work, PHP/Laravel, Rails, integrations and internal tools.
Yes. I can work inside your existing setup, whether that means Trello, Slack, Google Drive or another toolset. If there is no clear setup, I can help keep the workflow simple and visible.
Yes. That is usually the best way to start. A clear first task makes it easier to understand the project, the workflow and whether the collaboration is a good fit.
Yes, but that usually works best after starting with concrete development work. Once there is trust and context, I can help with decisions, workflows and the technical pieces around the project.
Yes. I’m based in Italy and work remotely with agencies and teams. I’m comfortable with async communication, short updates and shared documentation.