
I had my first two demos yesterday π
I'm currently building Site Command, a construction management platform for home builders & remodellers.
I had my first two demos yesterday evening - one in person, one remotely - both over an hour in length. They went really well, and I got some really valuable feedback.
I'm going to cut through the cruft and focus on the nuggets that I understand to be blockers to adoption. I think I'll be able to bring both these users on by the end of March - that's my goal. Ideally converted by the end of March, but we'll see how quickly I can get some of this stuff in place.
I have another demo lined up for next Monday, thought it's not exactly my target customer (they're a landscaper, not a home builder) but I still feel like there will be a lot to learn.
Couple takeaways from the past week:
Launch
At this stage, I'm starting to plan out a light "launch" -- telling family and friends about the product, posting it to Twitter, possibly even Product Hunt. Realistically though I'm kind of expecting to have to grind for a while to get customers, and then in a perfect world, let word of mouth drive the flywheel.
As always, I welcome thoughts, advice or guidance on any of this!
Haha I feel you on the production DB. Great work!
Yes @davey - as soon as my demos were over, I updated my DB backups from daily to hourly. Haha.
Cool
Great work, Tom! Please keep us updated with the progress you make on Site Command.
Thanks Tigran!
Hi, great design, are you using some kind of ux templates as a base? I will have to design a web-app soon and looking for shortcuts ππ
Hi @fastsyrup, thanks for the kind words! I use a slightly modified version of Bootstrap for this. I started wth Laravel Spark, which already modified a few small things like colours, and adds some simple shadows, and then I further modified colours to fit my palette (which was hard to land on!), some typography stuff (font and font weights mostly), and some spacing.
The structure is just using standard bootstrap 4 grids: rows & columns.
Happy to expand more if you have any specific questions!
thanks for the feedback. I use rails, so no laravel :) cheers
Design looks clean.
Are you customers primarily on the job site or at a desk with they'd use your software? I wonder if mobile views or an app would be crucial.
Thanks for the compliment :)
Re mobile: This is a great point!
The product is designed to be used mostly by admin & office staff and dispatchers - all of whom use desktops for their work.
However the crew receives notifications generally when they're in the field, and they need to update the status of jobs via mobile, so those portions of the functionality/app are all mobile friendly.
Keeping mobile in mind is very important if I actually want people in the field to interact with it as intended.
You might get away with text messages/email then as your means of notifications. "Low barrier to entry" and no need for guys in the field who may not be tech-savvy to learn a mobile app.
Fully agree! In fact, all of our "notifications" are emails right now, mostly with actions that can be taken straight from the email itself.
I am trying to work within people's current behavior as much as possible and reduce all undue friction.
During the demos, I showed how you can invite a person to be a crew member on your team. However, then the crew member needs to fill out a small registration form to actually become a part of the team.
This was flagged as "unlikely to happen" and I realized I needed to remove that requirement. Now administrators can fully add & register their crew, and the crew member only needs to click an email verification link one time. No more registration forms.