I'm Shilpa Rani. This is the engine I wish I'd had three years ago.

Chapter 1

Running three panels at once was a job in itself

I started reselling Instagram growth in a small way. A handful of creator clients, mostly through DMs, mostly word of mouth. By the second year I had accounts on three different SMM panels because no single one of them ever had every service I needed at a price I could actually mark up.

So my mornings looked like this. Open three tabs. Check balances. Compare rates for the service the client needed today. Pick a panel. Paste the link. Set the quantity. Submit. Copy the order ID into my own little tracker spreadsheet. Repeat for the next client. There were days I'd spend two or three hours just doing this dance before I got to anything that actually moved the business forward.

I kept thinking somebody must have built a tool for this. Nobody had. Everything in the market was either a panel itself, which meant more lock-in, or a thin wrapper that didn't really solve the multi-panel problem. I lived with the spreadsheet for almost a year.

Chapter 2

One afternoon, Panel A went down for two hours

I remember it pretty clearly because it was a Tuesday and I was eating lunch when the first client message came in. The panel I was using for most of my volume that month had become unreachable. I had twenty orders queued on it, none of them started.

I spent the next ninety minutes manually moving orders to Panel B and Panel C. Two of them got duplicated because Panel A came back up halfway through and started fulfilling them after I'd already replaced them somewhere else. Two clients got pinged twice and got annoyed. I issued two refunds out of pocket. One of those clients never replied to a message from me again.

That afternoon is when I realised the problem wasn't that I needed a better panel. The problem was that nobody was building the layer that sits on top of panels and actually thinks about routing, failover, and delivery timing. So I started sketching what that layer would look like.

Chapter 3

What I built, and why it looks the way it does

CurvePioneer is the tool I wanted in my own browser that Tuesday afternoon. It connects to whichever SMM panels you already use, by API, and treats them as a pool. You set a priority. Panel 1 is your default. If Panel 1 is busy or down, the engine moves the order to Panel 2 in under a second, and you see in the dashboard exactly which panel fulfilled which order. The duplicate-order problem I had does not happen here, because the engine knows what's already in flight.

The second piece is the curve. I spent a long time reading about how the Instagram algorithm treats sudden engagement spikes versus gradual real growth, and the gap between the two is honestly the difference between an account that grows and an account that gets quietly suppressed. So every campaign in CurvePioneer runs on an organic curve. A gradual warmup phase, a clustered peak during high-traffic hours, and a natural cooldown afterwards. You see the exact curve before you confirm the order. No surprises.

Then there's the agency layer, which got added once a few resellers I knew started using the early version. Each of their clients lives as a first-class Growth Account, with its own quota and history. When a launch needs to go out across thirty accounts at once, a single Growth Campaign fans out the brief and the engine paces every one of them independently. Cookies for the Instagram view-counter rotate quietly in the background so the numbers you see on your dashboard stay real and don't go stale.

None of this requires me to hold your money. Your balance stays with your panels. We're a routing and timing layer, nothing more. If you ever decide to leave, your panel accounts are still your panel accounts, unchanged. That part matters to me personally.