Open iteles opened 2 years ago
@iteles is your idea to research the existing CRM systems and pick a (relatively) low-cost one and start using it ASAP? 💭
Yes. But for that I need time.
This is an increasingly higher priority as it would free up a lot of my time currently spent reviewing the same info and most importantly free up headspace.
Need to review the original research doc and see if any of them are going to work!
@iteles 100% having a system would save you a ton of time. ⏳
Is the list of features in the OP ordered in terms of priority? 🔝
Feels like you're looking for a pretty niche product here ... 💭
My re-reading of the research doc and your feature list is that there isn't an obvious/immediate choice. 🔍
Want to sit down and go through the list and prioritise it (either solo or with me)? (T25M
) 📝
(I'd be very happy to help you with this. I've studied CRM UI/UX & features a lot over the years. 🤓 )
The list of requirements is really a list of the journey that the person goes through from first contact. I'll sit down and try to prioritise this a little better on Saturday when my head is in the Landim game.
Sounds good. Great to focus on the "journey" from the perspective of the prospective couple 💍 and correlate that to what needs to happen in our "back office" to streamline the process. 📥
I feel that we should take a look at how the established weddings sites do this 👩💻 and see if there are any "gaps" in their flow. 🔍 As you say, Saturday. 📆 👍
I have actually been speaking to a few photographers (rather than venues) who I have more rapport with and they seem to predominantly fall into two camps: very manual (like Excel spreadsheets) or Notion.
My problem here is mostly that the part I'm most keen on is the end of year analysis and most CRMs either don't do this or don't talk about it much!
Notion indeed ... 💭
Analysis/insights should be real-time to be useful. 📈 Otherwise the the org is not data-driven it's data retrospective. i.e. rear-view-mirror. 🪞
Happy for you to take a closer look at the features/requirements you need/want and prioritise.
But if you want to build something simple that gives you:
:statuses
you need to: dwyl/statusesThese are all features we will be building into the dwyl App
and we will be building in the next 6 months.
We will have APIs
for everything, so creating a custom UI/UX that is "Weddings Focussed" will be comparatively simple.
So if you want to Product-Own this from the events panning & management perspective/use-case; join the party! 🎉
Great! I'll be SURE to use the dwyl app APIs for this, it'll be a great test. In the meantime, I need something I can use just to keep data. in a useable way 😕
We need a system to be able to track all of our incoming requests, visits and conversions as well as the status of each person and the next action. This also helps us with follow-up like requesting Google reviews, post-wedding photos for social media, making sure everyone knows what's going on at all times without having to ask, etc.
I'm also keen to get a system in place that somewhat forces compliance. Because currently no one has to enter any information anywhere, it's all just in someone's head because 'it's in the emails' and things easily get missed, especially following up with potential clients.
It's an unnecessary cognitive load when you can just have a system that tells you what needs to be done next.
I'm looking for help on researching what is available out there! Not averse to paying a moderate sum for the right system that will keep us on track
Non-functional requirements
Functional requirements