Twelve-day close to a half-day close. Stacks was a material part of that.
I bought it for automated bank rec and JE upload and assumed I'd ignore the close calendar. The close calendar is one of the best things in it — one view of what's done, what's left, and who owns it, across six subsidiaries in NetSuite OneWorld. The JE upload being Excel-native is the sleeper feature; it effectively gives NetSuite the mass-edit capability it's never had, including for entries Stacks didn't create.
The broader upside is structural. Stacks doesn't make the last days of the close faster. It takes work off the last days entirely, so there's nothing left to compress. Close stops being a special event and becomes a Tuesday. Review collected by and hosted on G2.com.
We were an early customer. That comes with a cost, and the cost is your own time.
Being that early meant we were effectively part of the QA function. New capability arrives, we test it, we find what's broken, and we do that against live close deadlines with a six-person accounting team that has other work. The fixes come back fast — genuinely fast, faster than any vendor I deal with — but the finding is on us.
That trade was worth it for us. We got a product shaped around how we actually close, and a direct line to not only Leadership, but also subject matter specific developers. If you're buying Stacks today you're buying a more finished product and you'll do less of that, which is the correct outcome for you and probably a small loss for you too.
The other thing: the most valuable workflow we run through Stacks is one we invented ourselves, and nothing in the documentation or onboarding pointed at it. There is more in this product than the materials surface. Ask what else it does. Then ask again. Review collected by and hosted on G2.com.
