Lunch meeting with Josh Hanks. He's a friend from church and lives close by me in Richmond, UT. He has a fun startup story, and I found a lot of similarities to how I got started. He would go work for a company, figure out their processes, make improvements, and help them become better. Anyways, we had a fun chat and were able to find a number of similar circumstances as we got started.

Josh has used a few different CRM (customer relationship management) tools and I was going to pick his brain on likes, dislikes, wish lists, etc. See attached for some of my notes. Fun conversations and topics.

Here are a few takeaways:

- On SaaS (software as a service), here are some of the main complaints (not our product specifically but in general). People don't like extra steps, or required steps added by admin to do simple things. If the interface is too hard or too many clicks, it turns people off. If changes are made to flow, processes, or verbiage, people want to know (and yet they don't want to know everything - delicate balance).

- Mobile is really nice, but there are certain things that still work so much better on a laptop or desktop environment.

- Almost all of us have numerous channels and applications to use and balance. That could be emails, messaging, calendars, software, etc.

- People like to be able to edit things. If you lock it down too tight, it causes different problems. Let permissions, histories, and settings play in as needed to keep things secure but still open.

- People like options to control popups, reminders, feedback, snooze options, finished/completions, follow-ups, etc. They just want to control what hits them (virtually).

- There can be major pain trying to bounce and juggle too many calendars. For example, one for CRM stuff, one for projects, one for mail stuff, and one for personal. It can get kinda crazy. Lots of bouncing between multiple windows.

- We talked about one-to-many relationships and subs of time.

- As a wish list for CRM software - Josh loves to see recent activity, follow-ups, associated quotes, associated projects, progress and completion percentages, and even projections. Other things that are needed are good data, quick access, quick notes, and great drill-downs to other details and information.

- We talked lots about the need for custom fields and custom data points - per industry and per company.

- Opportunity costs and client acquisition costs - the hidden costs.

- The whole last part of the conversation flipped from CRM over to logging projects, hours (timecards per project or per location), quick notes, and logging mileage. Ideally, all of those things all nice and tied together. Josh was wanting and needing an app to do just those things (projects, hours, notes, and mileage). We talked about maybe making a mini version on some adilas features to make that happen. That could be really cool. The other need to that was availability to upload pictures and scans to those calendar events. Here's the kicker, we already do all of those things inside of adilas. We would just have to tweak it a little bit to make it flow, just like he wants. A small custom wire job of the existing tools and features. Pretty cool!

- Lastly, this is more for me, but when we build out fracture and adilas lite, I really want to revisit the settings and options for elements of time and scheduling. See element of time 8004 in the shop for more details. Lots of cool ideas.