Some technical work doesn't fit neatly into a few consulting days. Building major features, refactoring legacy systems or providing ongoing architectural guidance all benefit from continuity. That's where monthly collaboration comes in: a set number of days reserved for your project each month.
Instead of booking days ad hoc, I work on a monthly commitment, with the days blocked for you.
By Daniele Barbaro, Tech Lead & Software Engineer. Last reviewed .
A monthly collaboration means reserving a set number of days each month for your project. I agree on the commitment level upfront, either 12 or 16 days per month, and that time is blocked for you. You're not competing with other clients for attention during those days.
This isn't an on-call arrangement. It's planned, focused work. At the start of each week or sprint, I align with you on priorities. Throughout the month, I become part of your development process: attending relevant standups, participating in planning discussions and shipping code alongside your team.
The monthly structure provides flexibility within the commitment. If one week needs more days and the next fewer, I adjust. What matters is the monthly total and maintaining momentum on the work.
Roughly four days a week. Suits major initiatives.
Roughly three days a week. Suits ongoing improvements and guidance.
Which days they are depends on the work. What matters is the monthly total, not a fixed calendar.
The filled days are an example of how a month can look.
Everything from a standard consulting day applies, plus the benefits that come with sustained engagement.
Monthly collaborations typically go through phases.
I check in regularly about whether the arrangement still makes sense. If your needs change, I adjust the commitment level or transition to ad hoc consulting.
This model works best for teams that need consistent technical capacity without the overhead of a full-time hire, and when:
I offer two monthly commitment levels, each with a lower cost per day on longer engagements. The figures are monthly totals.
For teams that need substantial, ongoing engineering capacity. This is roughly four days per week, which works well for major initiatives: rebuilding core systems, implementing significant new features or providing sustained technical leadership.
At 16 days per month, I function as a fractional senior engineer. There's enough time for deep work, and the sustained context means less ramp-up between sessions.
For teams that need consistent senior capacity without full-time availability. This is roughly three days per week, enough for meaningful progress while leaving room for work that doesn't require senior involvement.
The 12-day option works well for ongoing maintenance and improvements, architectural guidance combined with implementation, or supplementing an existing team with specific expertise.
The rates for the other ways of working are on the rates page.
A monthly collaboration reserves a fixed number of days each month for your project, either 12 or 16. That capacity is blocked for you, so you are not competing with other clients for attention. It is planned, focused work rather than an on-call arrangement.
16 days per month costs €6,700 on commitments of six months or more, and 12 days costs €4,900. Single-month arrangements are priced slightly higher. Both options work out below the ad hoc daily rate of €480.
Days move within the month. If one week needs more time and the next needs less, the schedule adjusts. What matters is the monthly total and keeping momentum on the work, not filling a fixed calendar.
When there is a meaningful roadmap ahead, at least a few months of clear work, and the project benefits from someone who knows the codebase deeply and has been in the relevant discussions. If you need a week of help, booking individual days is simpler.
Month one is mostly about understanding the codebase, the team and the business. Months two to four are typically the most productive, once patterns are established. Longer engagements shift toward maintenance and knowledge transfer, with a regular check-in about whether the arrangement still makes sense.
If monthly collaboration sounds right for your situation, describe what you're working on. I'll discuss the work, timeline and what engagement level makes sense. There's no commitment in talking, and it usually becomes clear quickly whether this model would serve you well.
In TurinToolbox Coworking (opens in a new tab)
via Agostino da Montefeltro 2
Torino, TO 10134
The door is always open for a chat over coffee.