Agreed, a happy side effect from pursuing something worthwhile.
A heuristic that can help before starting anything new: "If I am guaranteed to fail at this, would I still do it?" [aiming for process instead of outcomes]
or "If I can tell noone about this, would I still do it" [aiming at interesting things for yourself, and not prestigious things]
I think what is nuanced here is the Saas teams need to setup a product, where this is completely needs based from a paying customer immediately.
80% value, 10% time. 100% done by one engineer, assisted by GPT to get the scope + spec ready.
I have had two meaningful responses to the form on the Notion site! Thank you very much!
"Using tools like Webfleet difficult to add multiple stops in one trip from one location to a central location. Routexl, does not group correctly."
"Long term projects cost control is very tough for my company"
If you would like to get a solution to either of these, please reach out!
leads_tractor0a@icloud.com
Hi Skeeter2020, thank you for your comment, appreciate it!
Your evaluation is perfect, it is very tough to identify your own pain point.
1. "GPT assisted" pain point identification is the first value add. To get to a clear statement of what you are experiencing. "routing with current tool doesn't allow for adding more stops"
2. A scoped document, "GPT assisted" again, that helps to run the purchase request up the chain. "a simple csv ingestion tool, running locally, that optimizes using openrouteservice, with output that works with your current logistics planning tool, $100/month for 12 months"
This is a work in progress.
And the typeform has a mistake, not collecting contact detail :-D thank you!
I agree, low-code tools are excellent to get these types of problems solves (CRUD apps for internal maybe?)
What I have in mind is:
- a forecasting tool (bit more insight into what is being done in the business, not just plain vanilla)
- Optimization tools: inventory, routing, sales, risk distributions etc.
- IoT integration for a small realworld tracking setup
- Specific business rules that need to be implemented in a Low-code tool
- Low code implementations (not everyone has the time, skill-set to get going with these providers)
What I am thinking of putting together is:
1. A good system prompt for a "product owner" who can really deeply care about the problem you are facing.
2. A second system prompt to write a product spec for the solution.
3. I'll be the first engineer on the platform, happy to build starting at $100 a month
4. Clients happy, engineers happy :-D
