business

Verdict

Submitted 5/13/2026, 12:03:19 PM · Completed 5/13/2026, 12:04:08 PM

6.5
pivot
The idea

Huge workbook, lots of tabs & macros--should I use something other than Excel?

Pain point
The user is managing a complex Excel workbook with numerous tabs and macros, leading to performance issues and scalability concerns.
Who has this problem
Purchasing professionals managing large-scale order and logistics data in Excel
Contradiction (TRIZ)
Wants to maintain complex formatting and macros while handling large datasets efficiently
Ideal final result
A scalable solution that maintains all current functionality without performance degradation
Suggested solution
Use Power Query for data management and consider transitioning to Microsoft Power BI for visualization while maintaining Excel for formatting and macros where needed.
Show original source text →
I work in purchasing for a large company and I have been using an Excel based tool to manage order and logistics data for years. I started writing macros to help with my tasks and now the workbook has nearly 20 tabs and 30-odd macros...things are getting way too beefy and I am wondering if I need to use something else to manage it. The general layout is: * 2 tabs with order data (one at PO level, one at line item level) using conditional formatting, XLOOKUP columns that reference other related data on other tabs, and macros for importing/processing new data. * 2 tabs to track receiving--one is 2 years of history and the other is a working sheet w/macros to pull receiving for a given number of days, look at the line items against one of the first 2 tabs, and mark lines that are not full order qty (among other things). Also has a macro that 'steps' through each unique PO# in receiving record and filters the first 2 tabs + receiving history tab for that PO# so I can enter things into purchasing system more efficiently. * Several tabs for reference data (logistics reports, truck schedules, etc.) which are either referenced manually as needed or actually feed into an XLOOKUP on the first tab. * 2 tabs with a macro to pull certain PO data based on several parameters, which I manually review and then use another macro to automatically generate emails to vendors. An AI told me I could use Sharepoint and Power BI to recreate the tool to be web-based and able to handle the volume of data I am working with, but I don't trust AIs lol. Anyone have recommendations of programs or strategies? I have no help from my company so I am doing this on my own to help myself.
TRIZ inventive level: 3/5· Principles: parameter changes, mechanical interaction
Synthesis verdict
**Pivot**. The idea of recreating the Excel-based tool using Sharepoint and Power BI as a standalone business venture has potential, but it requires significant adjustments to overcome the identified risks and weaknesses. The existing Excel tool's complexity can be mitigated by leveraging Power BI's data modeling and interactive features, and the market for procurement professionals is sizable. However, the lack of company support, regulatory and financial hurdles, and technical challenges make solo development of a viable, paid platform highly improbable within 6-12 months.

Strengths

  • - The existing Excel tool demonstrates a clear, high-value use case with tangible efficiency gains
  • - The market for procurement professionals is sizable, with over 10M professionals globally
  • - The proposed web-based solution can handle large volumes of data and provide a user-friendly interface
  • - The tool solves a real pain point: automating manual reconciliation, reducing errors in PO/receiving matching, and streamlining vendor communication

Weaknesses

  • - Lack of company support exacerbates regulatory, financial, and technical hurdles
  • - The target market likely lacks the budget for a new, potentially costly platform
  • - Transitioning to a new platform introduces significant dependency risks and a steep learning curve
  • - The revenue model is unclear, and pricing could be a challenge

Best angle

The tool should be positioned as a low-code SaaS product for procurement professionals, with a focus on automating manual reconciliation, reducing errors, and streamlining vendor communication, and should be developed with a clear understanding of the regulatory and financial requirements of the target market.

Panel verdicts

Viability

meta/llama-4-maverick-17b-128e-instruct

8.0

“The existing Excel tool's complexity can be mitigated by leveraging Power BI's data modeling and interactive features to simplify the replication of its functionality.”

The idea is feasible for a solo or 2-person team to build in 4-12 weeks. The existing Excel-based tool is complex, with multiple tabs and macros, but its functionality can be broken down into manageable components. The proposed web-based solution using Sharepoint and Power BI is a viable option, as it can handle large volumes of data and provide a user-friendly interface. The main challenge lies in replicating the existing macros and data processing logic in the new platform. However, Power BI's data modeling and DAX formulas can likely replace the XLOOKUP columns and some macros. The 'stepping' through unique PO#s and filtering functionality can be achieved using Power BI's interactive features. The email generation feature may require some custom development, but it's a relatively contained task. Overall, the technical complexity is moderate, and the timeframe is realistic.

Competition

nvidia/nemotron-3-nano-omni-30b-a3b-reasoning

6.0

“A tailored, web - based procurement tracker that integrates with the company's ERP and automates the current macro - heavy Excel process offers the most defensible differentiation, provided it can be built and maintained cost - effectively.”

The market already offers multiple solutions that address parts of this need: legacy Excel workbooks (the current tool), Microsoft Power Apps/Airtable/Smartsheet for low - code app creation, and full - featured procurement suites such as Coupa, SAP Ariba, or Oracle Procurement Cloud. These alternatives provide scalability, collaboration, audit trails, and integration with ERP systems, which the Excel - macro solution lacks. However, the user's specific workflow - combining order - level and line - item data, extensive XLOOKUP logic, custom receiving tracking, and vendor - email generation - does not map cleanly onto any off - the - shelf product, creating a niche where a purpose - built web app could add real value. The differentiation is therefore real in that it targets a precise, manually - crafted process that existing tools either over - engineer or under - support. Durability hinges on the entrant's ability to deliver a maintainable, secure, and user - friendly platform, secure buy - in from the organization, and continuously evolve the product; otherwise the advantage could erode as the user's needs change or as the company adopts a more robust ERP module. The key risk is the high upfront development effort versus the low cost of maintaining the existing Excel file, which may limit the viability of a sustainable business model.

Risk

nvidia/llama-3.3-nemotron-super-49b-v1

2.0

“Lack of company support exacerbates regulatory, financial, and technical hurdles, making solo development of a viable, paid platform highly improbable within 6-12 months.”

The proposed venture to recreate the Excel-based tool using Sharepoint and Power BI (or alternative platforms) as a standalone business venture is highly unlikely to succeed within 6-12 months due to the following specific failure modes: 1. **Regulation & Compliance Risk (8/10)**: Without company backing, ensuring GDPR, CCPA, and industry-specific data handling regulations for potentially sensitive logistics and vendor data becomes a solo burden, risking legal repercussions. 2. **No-Budget Customer Base (9/10)**: The target market (individuals in purchasing roles without company support) likely lacks the budget for a new, potentially costly platform, especially if they're accustomed to free (Excel) solutions. 3. **Platform Risk - Dependency & Learning Curve (7/10)**: Transitioning to a new platform (e.g., Sharepoint, Power BI, or alternatives) introduces significant dependency risks (platform changes, costs) and a steep learning curve for the solo developer (you), potentially leading to a non-viable product within the timeline.

Market

qwen/qwen3-next-80b-a3b-instruct

8.0

“The real product isn't the software - it's the automation of the tedious, error-prone procurement rituals that thousands of professionals perform daily with Excel, and they'll pay to stop doing it.”

This is a high-potential business idea because it targets a widespread, unmet need among mid-to-large enterprise employees who rely on brittle, homegrown Excel tools to manage critical operational workflows. You are not alone - thousands of procurement, logistics, and supply chain professionals use similarly complex Excel workbooks with macros, often without IT support. These users are frustrated, time-constrained, and desperate for scalable, reliable alternatives. The market isn't just 'people who use Excel'; it's specifically procurement analysts, logistics coordinators, and supply chain specialists in companies too large for simple SaaS tools but too under-resourced to justify enterprise ERP customization. Your tool solves a real pain point: automating manual reconciliation, reducing errors in PO/receiving matching, and streamlining vendor communication. A web-based solution built on Power Platform (Power Apps + Power BI + SharePoint) or even a lightweight Python/Streamlit app with a SQL backend could be packaged as a low-code SaaS product for this niche. The audience is sizable: Gartner estimates over 10M procurement professionals globally, and even 0.1% adoption (10,000 users) at $20/month = $2.4M ARR. You already have the domain expertise and prototype - this is a classic 'build it for yourself, sell it to others' opportunity. The key is packaging it as a turnkey solution with templates, training, and support - not just software. Competitors like Airtable or Zapier are too generic; your vertical-specific automation is the differentiator.

Monetization

mistralai/mistral-medium-3.5-128b

8.0

“Your tool solves a real pain point - productizing it for other purchasing teams could capture significant value.”

Your Excel-based tool demonstrates a clear, high-value use case with tangible efficiency gains (automated data processing, vendor communications, and PO tracking). The complexity (20+ tabs, 30+ macros) signals a need for scalability, but the core logic is already validated by your daily use. Transitioning to a web-based tool (e.g., Power Apps + Power BI or a lightweight SaaS like Airtable with scripting) could unlock multi-user access, real-time updates, and better data handling - critical for enterprise purchasing. However, the revenue model is unclear: if this is for internal use only, monetization is zero. If you productize it (e.g., sell as a niche SaaS for purchasing teams), pricing could be $50 - $200/user/month (tiered by features/data volume), with gross margins >80% (hosting + support costs are low). The conversion path would involve piloting with other purchasing teams, proving ROI (time saved, error reduction), and scaling via industry networks. Unit economics are strong if you automate onboarding (e.g., templates, tutorials).

Synthesized by meta/llama-3.3-70b-instruct · 10.9s