business

Verdict

Submitted 5/6/2026, 7:30:10 AM · Completed 5/7/2026, 1:30:19 AM

5.5
pivot
The idea

Truck driver in need of direction and resources.

Pain point
Truck drivers need an automated way to calculate route distances and times without relying on external tools or proprietary software.
Who has this problem
Self-taught truck drivers looking to optimize their freight runs
Contradiction (TRIZ)
Wants to customize calculations but lacks programming expertise to implement API integrations
Ideal final result
A self-contained Excel workbook that automatically calculates route metrics using native tools without requiring external dependencies
Suggested solution
Use a combination of Google Maps API with VBA macros to create a custom Excel add-in that handles route calculations internally, with clear documentation for non-programmers to modify parameters
Show original source text →
Ok so this might sound a little garbled but I am a noob and trying to teach myself this and having trouble knowing where to start. I am trying to build myself a spreadsheet that I can input addresses into and it will automatically calculate the miles the time so then I can use what the line haul is paying to determine whether or not it meets the criteria for what I need to make per mile before I accept or turn down the road. I have seen some premade distance calculators in Excel, but they are a little pricey and they are also proprietary, which means that I can't alter them to add an additional data that I need for calculating my runs. In the research that I've done I know that I need to get a Google route API key as use power query in order to get the API to function correctly in my Excel workbook. But what I don't understand is how to make everything native to my workbook. Example I would like column a to be start address and column B to be the finish address and to just be able to input the City or the address in each column and calculate it without having to open power query or a separate window or pull the data from somewhere else if that makes sense. So I know that I need to make some sort of VBA loop function and a macro inside my workbook that will do that for me, but this is where I've hit the wall of my very, very very small amount of knowledge. I know that I'm going to need to go into the API documentation and alter the programming to suit my needs because I don't need all of the information that the API key has in it. I only need the start to finish the miles and the time. So what I'm running into is threefold a how to alter the programming which some of my programmer friends have told me to just use Claude, which I get, but I still would like to learn a little bit, but I'm not too proud; B how to do a VBA loop function that will record what I needed to do so I don't have continue to open power query, and instead have it native to the workbook and three link all of that to a macro which I think I can figure out on my own because I do know that much. I hope this makes sense. I know that there are some videos out there that explain this to some degree but but it's usually for functions that don't apply to this. I appreciate any help and if I'm just being dumb and need to pay the hundred and 150 bucks to just have it done for me that would be the ability to modify the workbook then I'll just suck it up and do so. I just find that I'm fascinated by this and I do think it would be an interesting skill have I just feel like I need a bit of help finding the resources I need to teach myself this
TRIZ inventive level: 3/5· Principles: self-service, mechanical interaction
Synthesis verdict
**Pivot**: The idea has a clear niche and a plausible differentiation, but the defensibility is modest and depends heavily on the entrant's ability to keep the API costs low and stay ahead of platform changes. The project lacks a viable business model, relying heavily on personal technical development with no clear path to scalability or monetization. However, with focused learning and practice, a solo developer can build this in 4-12 weeks. The target audience is sizable, and the pain point is acute, making automation valuable. The idea isn't novel in concept, but its execution as a user-friendly, plug-and-play workbook with zero external dependencies could differentiate it.

Strengths

  • - Clear niche and plausible differentiation
  • - Sizable target audience with acute pain point
  • - Potential for high gross margins (80%+)
  • - Near-zero marginal cost per user after development

Weaknesses

  • - Modest defensibility due to API dependency and potential platform changes
  • - Lack of viable business model and clear path to scalability or monetization
  • - Dependence on individual learning curve and technical development
  • - Risk of API cost increases or changes in terms

Best angle

The project should pivot to focus on developing a scalable and monetizable business model, such as offering a subscription-based service or targeting a broader audience, while also addressing the technical challenges and API dependency.

Panel verdicts

Competition

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

6.0

“A native, free - tier Excel VBA solution that instantly computes distance and time from addresses could carve a niche, but its durability hinges on managing API costs and the declining relevance of VBA.”

The core need - quickly calculating line - haul mileage and time from two addresses to decide whether a run meets a per - mile profitability threshold - is already served by several existing tools: Google Maps Distance Matrix API (via paid add - ins), proprietary Excel distance calculators, and specialized freight - routing platforms such as Route4Me or Circuit. These solutions are either costly, closed - source, or require manual API calls and separate windows, which matches the user's pain points. A native Excel workbook that embeds a VBA (or Office Scripts) routine to call a free - tier mapping API, automatically pulls distance and duration, and presents the result in - sheet would indeed differentiate itself by being free, fully customizable, and eliminating external windows. However, durability is uncertain: Google's API pricing, usage limits, and potential policy changes could make the solution expensive or break it; VBA is also being phased out in favor of Office Scripts/TypeScript in the Microsoft 365 ecosystem, reducing long - term viability. Competitors could easily adopt similar native - Excel approaches or offer better free tiers, eroding the advantage. Thus, while the idea has a clear niche and a plausible differentiation, the defensibility is modest and depends heavily on the entrant's ability to keep the API costs low and stay ahead of platform changes.

Viability

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

8.0

“The project is feasible for a solo developer with some VBA and API programming knowledge, and the main challenge lies in learning and implementing the specific technical requirements.”

The idea is to build a custom Excel workbook that uses the Google Route API to calculate distances and times between addresses. The user wants to input start and end addresses in two columns and have the workbook automatically calculate the miles and time without requiring manual intervention. The technical requirements involve using Power Query to fetch data from the Google Route API, creating a VBA loop function to process the data, and linking it to a macro. While the user is a self-described 'noob', the task is achievable with some learning and experimentation. The main challenges are understanding how to alter the API programming, creating a VBA loop function, and linking it to a macro. However, these are specific, well-defined problems that can be solved with the right resources and guidance. The user has already identified some of the necessary tools and techniques, such as using Claude for API programming and exploring VBA loop functions. With focused learning and practice, a solo developer can build this in 4-12 weeks.

Monetization

mistralai/mistral-medium-3.5-128b

7.0

“A customizable, API-driven Excel tool for per-mile profitability in trucking can command premium pricing in a niche with high willingness-to-pay.”

The idea has clear utility for owner-operators or small fleets in trucking/line haul, where per-mile profitability is critical. The revenue model could be a one-time purchase (e.g., $150 - $300) or a subscription ($20 - $50/month) for a customizable Excel workbook with native Google Maps API integration, automated mileage/time calculations, and user-defined profitability thresholds. Unit economics are strong: near-zero marginal cost per user after development, with high gross margins (80%+). The key differentiator is customizability - competing tools are rigid or require external queries. However, the market is niche, and scalability depends on targeting the right channels (e.g., trucking forums, freight broker platforms). The main risk is execution: building a seamless VBA loop and API integration that feels native to Excel. If solved, this could capture value from a segment willing to pay for flexibility over off-the-shelf solutions.

Risk

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

2.0

“The project lacks a viable business model, relying heavily on personal technical development with no clear path to scalability or monetization.”

The idea's viability is severely limited by its narrow, personal scope, lack of scalability, and dependency on a single individual's learning curve without a clear path to monetization or broader appeal. The primary goal is to create a customized, proprietary tool for personal use, which doesn't translate to a viable business venture. Regulatory risks are low due to the non-public nature of the tool, but platform risk is high due to dependence on Google's Route API, which could change terms or pricing. Churn isn't applicable as there are no intended customers, and the 'no-budget customers' aspect is irrelevant since the project isn't designed for external use. The critical failure modes are: 1) **API Dependency & Cost**: Google increasing API costs or changing terms could make the project unsustainable. 2) **Lack of Scalability/Monetization Path**: No clear way to turn this personal project into a business. 3) **Dependence on Individual Learning Curve**: Project's success heavily relies on the founder's ability to overcome significant technical hurdles without a clear timeline or support system.

Market

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

7.0

“Independent truckers will pay for a simple, self-contained Excel tool that automates route profitability calculations without requiring technical skills or recurring fees.”

There is a clear, unmet need among independent truckers, owner-operators, and small freight brokers who manually calculate route profitability and are frustrated by expensive, inflexible commercial tools. These users operate on thin margins and need real-time, customizable calculations for miles, time, and pay-per-mile thresholds - exactly what this idea solves. The target audience is sizable: over 3.5 million truck drivers in the U.S., with an estimated 500,000+ owner-operators who are tech-savvy enough to use Excel but unwilling to pay $100 - $150 for proprietary software they can't modify. The pain point is acute: a single inefficient route can cost hundreds in lost profit, making automation valuable. While VBA + Google Maps API is technically feasible, the barrier to entry is high for non-programmers, which creates an opportunity for a turnkey, pre-built Excel template with embedded automation. The idea isn't novel in concept, but its execution as a user-friendly, plug-and-play workbook with zero external dependencies (no Power Query pop-ups, no manual API calls) would differentiate it. The market is willing to pay - many already do for similar tools - and the product can be sold as a one-time $49 - $79 download on platforms like Etsy, Gumroad, or a simple website. The real value isn't the code; it's the time saved and margin protection it delivers. With proper documentation and a demo video, this could scale into a niche SaaS-like product with upsells (e.g., fuel cost integration, toll calculations).

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