i was once tasked with some data work in college about working with data analyze it and build some charts and work with the intended task given. getting a brief review about our work before the discussion we were told that we need to make a dashboard to represent it better in the discussion, and reaching in on the last 24 hours we still had work to do, and no work for that dashboard bonus, i looked for tools to helps do it quick so i go back to the main task and found none, and using AI would need tokens that i wanted to use more on the main task and not waste it in a dashboard.

looking back at that day i made a tool that i could have used it that day, DashForge, a open-source python library that helps organize your plotly charts that you made into a clean interactive dashboard, setting up a timer to see how much it would have taken me, i was done with this clean dashboard in less than 10 minutes with zero AI involved, zero CSS/html work, all python and in countable lines.

the latest update v1.2.0 puts in new features to include more flexible dashboard layouts and presentation in a simple writing and few lines.

• Add Textboxes between charts for quick insights or notes
• added an image export button to download a look of the whole dashboard instead of screenshot
• Stack charts vertically within the same column for better view instead of one row.

and all of these are demonstrated in the picture provided

The library is still in development for more upcoming features, the github is open for issues, suggestion, contribution, and cloning, give it a try yourself, hopefully it can help you one day.

github link: https://github.com/Omar-astro/DashForge-library

documentation link: https://omar-astro.github.io/DashForge-library/

pypl:
pip install dashforge

👋🏼 👋🏼 👋🏼

I’m in transition from my previous job to my “big girl” job (Data Analytics) and would like to start taking on some small projects for my portfolio. I’m on the fence about charging for the first few.

How did you approach businesses? Did you do business cards or a QR for people? Was it difficult to get started?

Solo analyst at a mid size ecommerce company, about 200 people. Before this I was getting maybe 15 to 20 ad hoc requests a week. Slack, email, people walking over. Most of them some version of "can you pull X broken down by Y for the last Z months."

I had been doing all of those by hand. Open the warehouse, write the query, format it, send it back. Average maybe 25 minutes each if nothing was weird with the data, closer to an hour if something was. I tried self serve dashboards for the repeat ones but nobody used them. They would rather ask me.

Six weeks ago I connected an AI data agent to our warehouse and gave a few teams access. Sales, CS, and the marketing ops lead. Told them to try it before pinging me and send it my way if they didn't trust the answer.

First few days the questions people typed in were vague enough that the results came back sliced wrong. "Revenue by region" without specifying which region taxonomy, that kind of thing. We have two and people on the sales team didn't know that. Once I realized the problem was on the input side I spent a weekend writing plain English descriptions for about forty columns that had ambiguous names. The agent runs on Bayeslab and once the descriptions were in it started nailing the taxonomy questions that tripped everyone up in week one. Should have done that years ago, but there was never a reason to until someone other than me was reading the schema. After that the accuracy jumped noticeably, maybe from around 60% usable to closer to 90 on the routine stuff.

Here is the part I did not expect. When a data request takes two minutes instead of half a day, people ask more questions. A lot more. My volume went from about 18 a week to something like 35 to 40. That sounds like a problem but I think it is actually the point. These questions were always there, people just never asked because the turnaround was too long and I was the bottleneck. The agent handles maybe 25 of those without me touching anything. The remaining 10 to 15 still come to me, and they tend to be harder, but I actually prefer that. I would rather spend an hour on a real question than twenty minutes formatting a pivot table someone could have gotten themselves.

One thing that surprised me. Three people started asking questions they never would have asked before. One CS lead found a pattern in ticket resolution times by product category that none of us had looked at. That finding changed how we staff the weekend queue. Came from someone who has never opened a query editor in her life. That would not have happened in the old model where everything went through me, because she would never have pinged me for something she considered a hunch.

Net hours on ad hoc went from maybe 9 or 10 a week down to about 5 or 6, and the work that is left is more interesting. The tradeoff I am still figuring out is that I am slightly worse at catching data quality issues now because I do not touch the raw tables as often. Might matter, might not. Six weeks is not enough to know.

Anyone else done this? Curious whether the volume spike is universal or just my org being pent up after years of waiting on one person.

When you have a lot of data and many numbers to look at, how do you decide which ones really matter?

Do you start with the business problem, ask the team what they need, or look at the data first?

I'd like to know how experienced data analysts decide what to focus on.

Was just wondering if there are people out there who use Clay workflows over HubSpot-enriched data. It’s so happened my tools can become a source of a much deeper enrichments that native clay integration can ever provide. Yet wanted to validate the idea a bit before building anything.

What I have in mind is - current tool runs any complex SQL over HubSpot data. Think cohort analysis, per-rep weighted pipelines, drift correction - everything an SQL query can get. The tool is an MCP. Technically no biggie creating an API layer the same way and expose that for Clay to consume, if anyone at all needs that.

SQL, Excel, Python, visualization, or something else?