[thibaut_barrere]

I'm in the process of productizing a part of my ETL consulting services (building data intensive SaaS apps, ETL jobs or ETL-baked apps, or more generally any data transformation / data sync / migration), by shipping a reusable toolbox of Ruby ETL components (which is called Kiba Pro and is a yearly subscription enhanced version of http://www.kiba-etl.org) then later training resources for subscribers.

What I'm generating is improved skills & results in terms of data processing for the team, accelerated ETL workloads or "onboarding" on new ETL.

My biggest takeaway is that it's great to have both a sellable toolbox & a closely related consulting offer, because the components are nurtured by my consulting experiences and the reverse is also true. My efforts are fairly aligned together, which is great.

Before starting that, I made sure to be clear on IP and build a contract which makes me keep ownership & IP of the code I write & adapt, all while apportioning rights fairly for my consulting clients to use.