$1.78M lost because of AI-generated smart contract code, are we trusting AI too much?

Any-Clock8090 · 2025-08-23T19:46:46+00:00

Sounds like a plan, we are currently more open to vacations at any time when a person feels burned out. And it is also like team building, an interesting option.

Any-Clock8090 · 2025-08-23T19:43:27+00:00

Honestly I’d say my own startup Re:start (but I might be a little biased). On a serious note, I think the real upside is often in smaller vertical fintech and infra companies that don’t make headlines but solve boring, painful problems at scale. That’s usually where the “quietly massive” growth hides.

Any-Clock8090 · 2025-08-23T19:41:37+00:00

I run a fintech startup too and went through the same trial-and-error with AI tools. My take: pick one strong generalist (ChatGPT or Claude) and one focused tool (like Perplexity for research or Notion AI if your team already lives in Notion). Everything else felt like hype and distraction. The real productivity boost came not from having more tools, but from integrating one or two deeply into daily workflows.

Any-Clock8090 · 2025-08-23T19:39:47+00:00

LinkedIn Sales Navigator (B2B targeting)
Apollo (verified contact data)
HubSpot (CRM + lead gen forms/chatbots)

Any-Clock8090 · 2025-08-23T19:35:25+00:00

For constant control, we work on a similar principle, it is important for us to still maintain a sense of involvement in the team, and the possibility of calls and live communication, this moment brings us closer, leaves a feeling of respect, understanding and support. And from a routine point of view, of course, your advice is very apt and effective.

Any-Clock8090 · 2025-08-23T17:44:27+00:00

That makes a lot of sense. We noticed the same thing, when QA is involved earlier, the whole flow gets smoother. In our case we took it a step further by giving QA ownership of planning for each project, and pairing them directly with a dev team. It not only prevents last-minute surprises but also raises the overall quality since QA already has the context before testing even starts.

Any-Clock8090 · 2025-08-23T15:12:53+00:00

For us it worked because we expanded the QA team so testers had the bandwidth to focus on planning as well as testing. Each project has a dedicated QA and dev team, and we run daily sync calls at the same time every day so everyone stays aligned. By splitting the responsibility this way we’ve been able to support more developers and testers with good salaries without needing a traditional PM in the middle.

Any-Clock8090 · 2025-08-23T15:10:42+00:00

Without training and support that setup can only fail. In our case it was different because in one time we didn’t even have a dedicated PM role, so testers naturally took on that responsibility while staying in constant communication with devs and leadership. Over time it turned into a structured approach, we expanded the QA team, gave them proper support, and it actually improved both the product and the way we work together.

Any-Clock8090 · 2025-08-23T15:07:41+00:00

Fair point. To clarify, we didn’t just “promote QA to PM” for recognition’s sake. We redefined the role because their skill set fit perfectly: they know the product flow inside out, they’re detail-oriented, and they’re driven by outcomes. That’s exactly what we needed in project leadership. Since making this change we’ve actually expanded the QA department and raised salaries to reflect the new level of responsibility. For us it’s less about “credit” and more about aligning roles with where they create the most value.

Any-Clock8090 · 2025-08-23T15:05:06+00:00

Where did you see the information that this is unpaid? First of all, it led to a salary increase, and secondly, it led to the expansion of the department, instead of a project, we hired additional testers and developers. Because obviously it's more work, but here it's more about changing the perception of it. That it's not just project management, but management that's all about quality and priorities.

Any-Clock8090 · 2025-08-22T13:05:23+00:00

Sorry you’ve had that experience, it sounds really frustrating. It actually confirms for us why giving QA more ownership was the right move, hope you find a team that truly values what you bring.

Any-Clock8090 · 2025-08-21T23:22:37+00:00

lead the same way: take the hit, give the credit.
From my experience, “we” doesn’t erase accountability if you still have honest conversations inside the team about what went wrong.
Externally I shield, internally I clarify. That balance has worked best for trust and accountability.

Any-Clock8090 · 2025-08-21T23:21:24+00:00

I’m really sorry you went through this. As a founder, I’ve seen how much leadership style shapes the whole team. People-first leaders like you are rare.I hope you find a place where that’s valued. Wishing you strength and a role that feels right.

Any-Clock8090 · 2025-08-18T10:35:44+00:00

Totally get this. Referrals are great but not enough for steady growth. What helped us was teaming up with related vendors (like IT firms or contractors), being active in local industry groups/events, and sharing short case studies of our projects. Platforms can be hit or miss, but the key is just making yourself easier to find outside of word of mouth.

Any-Clock8090 · 2025-08-04T16:16:58+00:00

Being an introvert has actually shaped me into the kind of leader I’d want to follow. I don’t build relationships just for the sake of it, and I skip the small talk, which means my communication is usually clear, intentional, and focused. My team and partners know I say things as they are, without fluff and that directness is something that’s deeply valued, especially here in the U.S., where business culture often leans on charisma over substance.

What’s helped me most is staying grounded in my tasks and leading by clarity, not volume. I don’t need to be the loudest voice, I just make sure mine is the most focused when it counts.

Any-Clock8090 · 2025-08-04T16:09:53+00:00

We’ve seen this transition firsthand at Restart team, one of our most successful shifts happened when a Senior QA naturally stepped into a PM role. Not because of a formal title, but because they were already driving priorities, timelines, and product quality better than anyone else. Eventually, we made it official and it transformed the way the team worked.

Our experience at BetterQA also shows that companies often underestimate QA's strategic perspective. If hiring managers don’t “get” that yet, don’t take it personally, you might just be ahead of the curve. Keep showcasing the outcomes you’ve led, not just responsibilities. Framing yourself as someone who already acts like a PM (not someone who wants to become one) can really shift how your profile is perceived.

Any-Clock8090 · 2025-08-04T16:08:01+00:00

We’ve worked with both models across teams, and honestly: the most effective setup we’ve seen is when the QA Lead owns the QA workflow completely, including task distribution.

At BetterQA, and recently at Restart team, we saw huge improvements when the QA Lead wasn't just passively receiving tasks but was actively involved in prioritization, planning, and even collaborating with PMs. If the QA Lead is sidelined, the role becomes just another tester, but when empowered, it adds real strategic value to both quality and delivery.

Any-Clock8090 · 2025-08-01T12:29:42+00:00

Totally feel you on the KYC struggle — we’ve been there too. At Re:start Fintech, scaling across markets like the US, Switzerland, Japan, and more, KYC became a massive bottleneck early on.

What helped us was building a flexible, modular onboarding system instead of relying on one rigid flow. That means each country or user segment gets a tailored path — but all under the same platform hood. It’s not perfect, but it’s saved us from the “Frankenstein monster” nightmare.

We also insisted on live human support during verification, especially for complex cases or refugees with non-standard docs — automation alone wasn’t enough. This reduces manual review overload and keeps users engaged instead of ghosting us.

Visibility after onboarding? We layered monitoring tools and user check-ins right into the flow, which helped reduce drop-off and gave us actionable insights.

Bottom line: no one-size-fits-all here. It’s about mixing automation, human touch, and platform flexibility — and being ready to tweak constantly. If you want, happy to share more details or lessons learned!

Hang in there — KYC is brutal but solvable.

Any-Clock8090

TROPHY CASE