| i've been building software as an engineer for 20+ years for big cos and indie projects. ... they all kinda start out the same:  i essentially boil it down to 3 steps: 1. Customer sends you data…
2. You manipulate the data…
3. You send the data back to the customer… this is how i start the process... i figure out the fundamentals. a few examples: Dating / Matching Service:
- You send me your dating preferences (via form)…
- I’ll manually sort / categorize / match you with the “best fit” (manipulating data)…
- I’ll send you your match (and you’ll pay me)!
Customer gets a potential match and you get paid. Collecting, Delivering Daily Standup Notes:
- You (team) sends me daily standup notes (via web form)…
- I’ll auto-magically categorize notes into business unit (ops, dev, design, legal, marketing, etc)…
- I’ll send you (the team) all the notes related to your specific business unit!
Individuals and teams are updated, aligned, and they now have the necessary info to do their job well. Blogging Publishing Template:
- You create a simple form to capture blog post ideas…
- I’ll sort it based on length and other metadata…
- I’ll send you the template to use for your post (with API access?)!
Customer get a “best practice” blogging template and you get a repeat customer (monetization)? ... so, that gets me a baseline of the problem, the customer, and a very basic product... this can oftentimes done with #nocode or with existing services... you can almost fake a lot of this in the beginning. if you've got the customer and the value right... then you can iterate on the product, part #2 which was once a manual (or semi-manual process) and then you graduate or iterate or evolve or level-up the product to be more automated over time. this is a land-war of sorts... and will take many attempts to get it right. don't give up. ping me if you need anything: john [at] yen [dot] io |
