A journey from excel to python

2 years ago I joined the Cashstory company to help on the tech side people we do data transformation for companies.
They were doing python script to automatize or partially automatize data transformation in the DataViz tools.

What I saw was Terrible!

A black box, a limited tool, a lot of duplicated code, wow!
So much far from the coding culture, I’m from.
Yes, I joined a team of financial people who learned code because they were frustrated to be limited by excel!
so I started to help them, but not as they thought.
They thought I will code for them, instead, I coded tools to make life easier!

we started by having a templating system, to help them to have a basic data workflow.

Then we created a tool to help find a workspace where each client related tools and script are accessible!
It was already a great product, but not enough, the core problem was the BlackBox where they code.
The DataViz tools they used to allow to create a script but in a too much-restricted way for them.

They were limited by the code.

WHAT !?
They were using python but inside the tools, they were not free to install any lib and do things as they need.

So we searched for an alternative, and clearly, Jupiter showed up straight.
They tried it and liked it.
But, even if Jupiter is awesome, send a notebook in production is not easy for a non-tech.

That is the seed of our second product.
Naas the product I am the proudest of my life.

The funniest thing, that probably the most simple one.

with Naas, you write your notebook in Jupiter as always, no fancy override UI who broke the experience of the most advanced data scientist tools of the world.
Add just another simple line and your notebook is in production:
Naas.schedule.add(“0 9 * * *”)

It will be run every day a 9:00

The craziest part :

they started to enjoy this too much, they started to script all in our company with notebook, cold e-mail, lead generation, analytics, update of other apps, website.

The story continues too far I solved all the pain by tools they get power not by doing the job for them.

It bringer us the API feature, run a notebook by calling URL.
Then the assets one, expose result of a notebook, any file output, or notebook itself.
Send an e-mail with data, scale notebook resources, etc.

People were asking us where to get it

At this point we discovered, what I was doing was a product, not just a tool.

So we decided on 2 things :

open-source it
Sell it on a cloud solution

So now we have done the open source part, we plan to start to sell the cloud solution it starting 16 November.

We need feedback on our landing :
https://naas.ai

Does this give you the same feeling as me?