What You Can Do Next: Closing Recap

Now what? The Day 2 wrap-up is the bridge between two days of demos and the rest of your quarter. Pick one thing to act on rather than trying to adopt everything at once. Stay close to your account manager. Plan around the new UI becoming the only UI in June. Get a concrete read on what lands when across the new architecture and the migration roadmap. And get a candid answer on why CalcuQuote commits to initiative-level direction every three to six months rather than dated feature lists: because customer asks reshuffle the queue every week.

Headshot Kaitlyn Tredaway_250x250px
Kaitlyn Tredaway
Chief Operations Officer, CalcuQuote

Kaitlyn Tredaway closes Day 2 with a practical view on what to do next. The focus is on prioritising adoption, understanding the near-term roadmap, and setting realistic expectations around how features evolve so teams can plan and act with clarity after the event.

Request a Demo

Key Takeaways

Most customers are not using everything they already pay for

The blunt opener: catch up on existing capabilities before reaching for new ones.

  • There is not a single company in the room using everything they already pay for
  • Existing capabilities to revisit: configuration view, goal seek, summary customisation, multi-year quotes
  • New features land faster when you are already on the current foundation

New architecture migration timeline, and what is still missing

Two modules are live on the new architecture. The rest catches up in June.

  • RFQ form (first step) and summary tab (last step) are already on the new architecture
  • The rest of the workflow migrates through "close the gap" features expected in June
  • Today’s gap: auto-apply markup rules and auto-cost rules do not yet exist in the new architecture
  • You can migrate now and accept the gap, or wait 

New UI: on for everyone in May, no opt-out from June

Restated from the Day 1 UX session for emphasis.

  • Throughout May the toggle is available
  • From June onward, the new UI is the only UI
  • The team explicitly cannot keep supporting two interfaces

The roadmap is intentionally not feature-dated beyond about 60 days

Initiative-level direction every three to six months, not feature-by-feature dates.

  • The team knows what is in the next release and is fairly confident about May
  • June and beyond shift based on inbound customer asks
  • One customer requests a feature, seven more agree, the queue reshuffles
  • Internal migration to a GitHub-based dev system is starting to make even initiative-level visibility possible

PFAS, country of origin, and cage codes land in Scrub My BOM on Friday

A near-term compliance win, already on the calendar.

  • PFAS detail is already in Scrub My BOM (answered Day 1)
  • Friday of the conference week: additional Accuris fields go live
  • Includes country of origin, cage codes, and several others

Quick answers on customer-submitted questions

A rapid-fire round on reporting, notes, SearchCQ, and suggest-alternates.

  • Reporting options are available now beyond the standard subscription, ask your AM
  • Embedded in-app report viewer expected end of Q2
  • Notes on quote lines during material broadcasting already exist
  • SearchCQ will not be expanded into a full BOM-import/pricing tool. A lightweight Scrub-My-BOM.com-style API import is possible but low priority
  • Suggest alternates sometimes returns no results. Send examples to alex@calcuquote.com so the lookup logic (Accuris form/fit/function plus vendor API alternates) keeps improving