Hi,
I'm 24M and have been around 2 yrs working as a developer. I want to start building something of my own, but I am not getting any good ideas or problems to work on. So if anyone here has any tech-related business idea or a problem you might be facing in the sector you are working in. Would love to talk, and if it sounds good, we can work together to build something.
Currently use GHL, looking at Attio and Close
Any other ones I should be looking at?
Hello, we are working on invoicing software and wanted to contact more potential customers. We did direct contact, but that is really slow.
We are looking for some CRM, where can we add all potential customers, also the existing ones I would say.
It will be for two people at start, ideally free from beginning. Happy to pay later if we get more paying customers.
What features I am looking for.
Optional features:
Do you have such a recommendation? Or what features I would need, but I don't know currently? :)
Looking for some CRM recommendations because I’m currently trialling Folk and I’m not completely sold on it.
There’s only two of us at the moment. Probably 95% of what we do is outbound, either physically going into businesses or calling them. My associate will do most of the initial prospecting, gather whatever information she can, and then either follow up herself or hand the lead over to me once they’re interested.
I’m less interested in a CRM being a prospecting tool and more interested in it being really good at capturing what we find and making sure we follow it up properly.
Typical example would be: she walks into a business, owner isn’t there but staff say they’ll be in Monday. She needs to quickly add the business, contact/details/notes, then set an action to go back Monday. If she speaks to the owner and they’re interested, she can then put an action in for me to call them, arrange a demo etc. From there I’d want a simple pipeline through demo > quote > won/lost.
A few things that are important:
Really quick contact/company and note capture
Custom fields (turnover, current supplier, current POS/software, industry, number of locations, pain points etc.)
Next action/date and reminders
Last contacted
Call lists / ability to filter a list and work through it
Easy handover and task assignment between the two of us
Simple pipeline
Good mobile app would be a big plus as we’re out in the field a lot
Nice to haves would be WhatsApp integration, email integration with open/link tracking, and some sort of ChatGPT/AI integration.
One thing I’m not loving about Folk is the separation between Company, Person and Deal. I understand why CRMs work that way, but for us 90%+ of the time there is one business, one main decision maker and one sales opportunity. A lot of the useful data belongs to the business itself because we’ll want to filter it later for prospecting — e.g. show me all pubs using X POS with £20k+ monthly turnover that haven’t been contacted recently. Having to jump between three different records feels like more admin than we need.
We’re not doing massive automated outbound sequences or managing hundreds of inbound leads. It’s much more hands-on relationship selling and we want the CRM to make sure nothing falls through the cracks.
I’ve looked at Close, Folk, Fluid, Attio etc. but I’m open to anything.
What would you use for this? TIA
I've been experimenting with agents for GTM work and I'm starting to think building the agent itself might be the easy bit.
The annoying part is giving it enough context to be useful.
If I ask something about an account, I'd want it to already understand the people involved, previous emails, calls, notes and whatever has been happening with the deal. Having an agent research something is less impressive when I first spend ten minutes explaining the customer to it.
I'm curious how people are solving this in practice. Is your CRM becoming the context layer for the agents or are you feeding customer context into them some other way?
And once they have that context, what work are you comfortable letting them handle?
I'm trying to understand how smaller VC/investment teams deal with relationships because they seem to get messy fast.
One person might be a founder at a portfolio company, an angel in another deal, an LP connection and someone we'd potentially introduce to another founder later. Six months pass and remembering why somebody matters can involve searching emails, old notes and probably asking whoever originally knew them.
The CRM options I've looked at mostly seem good at storing the information. I'm more interested in whether they help you make sense of it later.
Anyone here managing this for a small investment team? What does your setup handle for you day to day that you wouldn't want to go back to doing manually?
Hi I am a fresh grad. I built CRM to learn enterprise software architecture, check it in google unithreadcrm says Connects with people. You can freely check it, click test demo to try. I already provided sample data. It is so easy to use, please provide feedback. Thanks!
Hey “RevOps and DataOps”,
Working on something in the revenue operations space and trying to wrap my head around a specific problem before I go too deep.
The pattern I keep hearing is that dashboards tell you something is wrong, but not what, where it started, or how long it's been happening. By the time a number turns red, the damage is already done and tracing it back across your CRM, data warehouse, billing platform, and whatever else is in the stack can eat up hours.
Curious if this is actually a painful thing for RevOps or DataOps teams at software companies, or if most people have figured it out already.
Two questions if you have a minute
Even a short "yeah this is annoying and here's what we do" type reply would help a lot.
Thanks.
Do NOT USE THIS COMPANY
They will force you to signup for the $694.00 plan
You will be forced to also sign up for 97.00 a month “coaching plan” they will be on it when it comes to signing up but for coaching they will be like ghosts.
If you don’t cancel and you get billed the 97.00 they will not refund and they will cancel your account if you dispute the transaction with your bank . So the $694 plan that you paid for will be for no reason. Also the platform itself doesn’t work very well.
Save yourself this headache and avoid at all costs. Complete waste of time and money.
I keep noticing the same pattern in RevOps / Sales Ops teams:
A dashboard turns red.
Everyone knows something is off.
But nobody knows where it broke without manually digging through CRM records, syncs, lifecycle stages, routing logic, billing data, or duplicate records.
By the time someone finds the root cause, the damage is already done.
From conversations I’ve had, the hardest part usually isn’t seeing that a metric dropped.
It’s figuring out:
- what changed
- where it changed
- whether it was data, process, or automation
- and who is supposed to catch it before revenue is affected
I’m curious how people handle this.
- Do you rely mostly on dashboards and manual investigation?
- Have you built alerts for specific failure points?
- What kinds of issues actually cause the most leakage
When it comes to small businesses and CRM adoption, the most common failure pattern seems to start with someone deciding to implement everything at once, the team becoming overwhelmed, adoption collapsing, and two months later, half the team going back to their spreadsheets.
The instinct to go all-in from day one is entirely understandable. The business has finally committed to the tool, and it wants to extract maximum value from it as soon as possible. The problem is that these teams treat the implementation process like a product launch instead of the measured organizational change it should be.
What tends to work better for small businesses is establishing a much narrower starting point. Before going live, ask, “What does this CRM absolutely need to do in the next 90 days to protect revenue?” So, just the minimum that makes the core sales work demonstrably better, rather than everything at once.
For most small business teams, that boils down to three core things:
Everything else, like automation, advanced reporting, marketing workflows, and integrations, can wait until the team is actually using the core functions consistently.
When phase one is limited to what people need to do their jobs today, the CRM becomes useful immediately. Early wins create internal advocates. And those advocates are more effective at pulling colleagues into the system than any training session.
The tricky part is that this approach requires resisting the pressure to show off every feature the tool has. That's harder than it sounds when leadership is excited about what the platform can eventually do.
Has anyone found a good way to manage that expectation gap during rollout, especially when stakeholders want to see the full picture right away?
We sent the same short, polite connection template to about 500 prospects over two weeks. Acceptance rate stayed under 15 percent and replies were almost zero. A colleague later showed me his inbox and my message looked identical to dozens of other pitches he had received.
Sending the exact same note to everyone clearly gives the reader nothing personal. For those of you running outreach through your CRM or sales sequences, what changed your acceptance and reply rates once you stopped using one generic template?
Login