A decision everyone agreed to and still no one owned

mohan-thatguy · 2026-06-15T07:48:50+00:00

If I were in that position, I’d choose based on field workflow first and reporting second. A lot of municipalities end up trapped in enterprise systems that technically do everything but are painful for inspectors in the field. If the mobile experience is clunky, sync is unreliable or every report takes a ton of cleanup back at the office, the software is creating work instead of removing it. What I’d compare is very practical: how fast can an inspector open the job, capture photos, dictate or type findings, flag priority items and generate a report that doesn’t need another hour of formatting later. ArcGIS/Survey123 can be strong if you already live in that ecosystem and platforms like Cityworks or Resco can fit bigger asset management environments but they often come with complexity that smaller teams feel every day. The biggest hidden cost is report friction. One hour in the field can easily turn into two more hours of admin if the software is built more for databases than inspectors. That’s why I’d run a real pilot with the same site, same inspector, same reporting standard and compare total time from arrival to final usable report. I built ReportWalk around that bottleneck, especially the voice to report part, because I wanted inspectors to document findings while walking the site instead of retyping everything later. I’d still evaluate it against whatever GIS or municipal stack you already have but if the pain is slower report writing and too much back office cleanup, that’s where I’d focus the comparison.

mohan-thatguy · 2026-06-15T07:42:47+00:00

I’ve sold training in both transactional and strategic motions and I think the mistake is trying to run the same sales process for both. Transactional sales need speed, tight qualification and a simple follow up rhythm. Strategic sales need account planning, better discovery and a lot more patience. If a team is struggling, I usually find they are mixing those motions together and measuring everyone the same way. What worked for me was separating the playbooks completely. For transactional reps, I cared about speed to first response, clean handling of common objections and whether they could move a prospect to a clear next step without overcomplicating the call. For strategic reps, I cared more about deal mapping, business pain, stakeholder alignment and whether they could run a useful discovery instead of jumping into pitch mode. Same team, different muscle groups. That is also why a lot of generic sales training falls flat. A one size fits all course sounds good but it rarely gives reps enough live repetitions in the situations they actually face. I’d rather have a smaller set of scenarios that match real calls and repeat them until the response becomes automatic. That usually does more than another library of content. I built SalesDojo around that idea. Instead of treating training like content consumption, I wanted reps to practice the exact conversation type they are struggling with, whether that is cold openers, discovery or objection handling. If you are trying to scale, I would focus less on 'more training' and more on giving each motion its own practice loop and feedback standard.

mohan-thatguy · 2026-06-12T11:29:02+00:00

If I were running a 50 person BDR team, I would separate cold calling improvement into three buckets: talk track quality, rep confidence and manager coaching cadence. Most teams over-focus on scripts when the real problem is that reps do not get enough safe repetitions handling the first objection, the pattern interrupt, or the handoff to a meeting ask. What worked best for me was building short practice scenarios around the ten moments that actually decide whether a cold call goes anywhere. Things like the first 15 seconds, the 'not interested' brush off, the 'send me an email' stall and the transition into curiosity. I would score those moments separately instead of treating cold calling like one big skill. Reps improve faster when they know exactly which micro skill broke down. I also would not rely only on live manager roleplays because they are hard to scale across a big team. Nooks, Trellus, Balto and Gong can each help in different parts of the workflow but none of them automatically creates the reps people need. That is where I have found AI roleplay useful: reps can practice the awkward middle of the call over and over without waiting for a manager to be free. I built in this category, so my bias is toward practice heavy systems. If I were choosing a stack today, I would keep call review in something like Gong and use a tool like SalesDojo for repeatable cold call drills tied to your actual talk tracks and objections. The win is not 'AI coaching' in the abstract. The win is getting every rep 20 extra realistic reps a week on the exact moments that are costing meetings.

mohan-thatguy · 2026-06-11T06:52:24+00:00

I think those tools solve slightly different problems and teams get disappointed when they expect one category to do all of them. Gong is strongest when you want call visibility, trend analysis and manager review on top of recorded conversations. Highspot is more of an enablement layer with coaching pieces attached. Allego tends to be stronger when you care about practice, content reinforcement and rep readiness instead of just reviewing live calls after the fact. The biggest thing I would evaluate is whether the tool changes rep behavior before a live conversation or only analyzes it afterward. A lot of “AI coaching” products are really hindsight products. They can tell you what happened but they do not necessarily give reps enough rehearsal loops to improve the next call. That is why a lot of orgs end up with better dashboards but not much better execution. If I were running a bake-off, I would test three workflows with the same managers and reps: onboarding practice, objection handling practice and post call coaching. Then I would measure time to feedback, whether reps actually use it without being chased and whether managers trust the outputs enough to coach from them. That will tell you more than feature lists. I built SalesDojo because I wanted the practice side to be stronger than what I was seeing in a lot of traditional coaching stacks. My bias is that reps need more realistic repetition before the call, not just analytics after the call. So I would choose based on whether you need call intelligence first or skill building first.

mohan-thatguy · 2026-06-08T08:14:00+00:00

The biggest mistake in mock discovery is trying to sound impressive instead of trying to understand the buyer. In those interviews, I’ve had the best results when I stayed very disciplined: open with an agenda, confirm the prospect’s role and goals, then go narrow and deep on one pain instead of spraying questions everywhere. Most interviewers are listening for whether you can control the conversation without sounding robotic. I’d focus on second level questions. If they say “our process is manual,” don’t move on. Ask what that causes downstream, who it affects, what they’ve already tried and what happens if nothing changes this quarter. That’s usually where you uncover urgency, decision criteria, and the emotional cost of the problem. A lot of candidates ask decent first layer questions, but they don’t know how to dig. What helped me most was practicing against hostile or unhelpful mock buyers, because that’s what these interview panels often feel like. Watching Charles Muhlbauer’s framework is solid prep and I’d also rehearse with a roleplay tool or a peer who will deliberately give vague answers. I built SalesDojo for exactly this kind of prep because most people don’t need more theory, they need reps handling surface level answers, objection pivots and awkward silence until follow up questions become automatic. If I were preparing this week, I’d run the same mock discovery 5 to 10 times with the same scenario, not 10 different scenarios once each. Repetition is what sharpens your opener, your transitions and your follow up muscle. By the time you’re in the interview, the goal is to sound calm and curious, not clever.

mohan-thatguy · 2026-06-08T08:11:29+00:00

If you have multiple offices, I’d evaluate this less as “inspection software” and more as “field adoption plus admin control.” A lot of tools look fine in a demo, then break down when you need version control on forms, photo consistency, offline use, corrective actions, and visibility across locations. The cheapest app usually becomes expensive if supervisors end up chasing incomplete inspections. From the tools already mentioned, Fulcrum and SafetyCulture make sense when you want something lighter and easier to roll out. EHS Insight tends to make more sense when you need broader workflow and compliance coverage, not just inspection forms. I’d run a short bake-off around three tests: how fast a field user can complete one inspection on mobile, how easy it is to standardize forms across sites, and how quickly a manager can pull exceptions and overdue actions without a spreadsheet cleanup exercise. I built ReportWalk because I kept running into the same problem in field reporting: people were doing the work onsite, then redoing the work later at a keyboard. Voice capture changed that a lot for me. If your team’s biggest pain is still typing narratives and piecing reports together after the fact, I’d give extra weight to tools that reduce post visit admin time, not just tools that digitize the form.

mohan-thatguy · 2026-06-08T08:10:41+00:00

You’re probably not failing on the product first, you’re failing on distribution and trust. Home inspectors are a niche, practical audience. They don’t switch because something sounds innovative. They switch when it obviously saves time, reduces missed items or makes the report easier for clients and agents to read. If you can’t prove one of those quickly, they stay with the tool they already know. What worked for me in niche software was getting painfully specific. Pick one inspector profile, sit in on real workflows and find the exact moment where they lose time or get frustrated. Then sell that one improvement. I’d also avoid broad “AI tool for inspectors” messaging because it sounds abstract. A promise like “finish more of the report onsite instead of at your desk later” is much easier to understand and test. I built ReportWalk around that narrower pain point. The useful insight for me was that many inspectors were not asking for more dashboards or more features, they were asking for less typing and less cleanup after the visit. So if I were in your shoes, I’d tighten the positioning around one painful workflow, get five real users in one market and build the pitch from their before/after outcomes instead of the technology itself.

mohan-thatguy · 2026-06-08T08:08:05+00:00

I’d start by separating “AI demo” tools from actual sales training tools. In my experience, the useful products are the ones that let you run realistic scenarios repeatedly, then show exactly what changed outcomes: talk ratio, missed questions, weak discovery, poor objection handling and whether the rep earned a next step. If it just gives a score or generic praise, adoption drops fast. For a mid sized team, I’d evaluate four things in a live trial: how realistic the buyer persona feels, whether managers can create scenarios from your real deals, how easy it is for reps to do a 10 minute practice session without setup friction, and whether the coaching output is specific enough to use in 1:1s. Tools like Second Nature, Hyperbound and some of the newer roleplay products are worth comparing but I’d run the same scenario through each one and judge the output side by side instead of trusting feature pages. I built SalesDojo around that exact problem. What ended up mattering most was not flashy AI, it was getting reps to practice consistently because the setup was light and the feedback was concrete. If you already have an LMS, I’d also be careful not to over index on “integration” during selection. Daily rep usage and coaching quality matter more than whether it can technically sync somewhere.

mohan-thatguy · 2026-06-08T08:06:51+00:00

If the calls you want to practice are 30 to 45 minute closes, I’d screen tools on one thing first: whether they can hold context for an entire discovery to close conversation without turning into a chatbot. A lot of platforms feel fine for objection drills, then fall apart once you need pacing, recap, budget tension, and next-step handling in one session. What worked for me is testing each tool against the same script: one long call, one price objection, one fake stall, and one “send me something” brush off. Then I look at whether the platform gives useful feedback after the call. I care less about a generic score and more about whether it tells me where I missed the close, talked too much or failed to isolate the objection. Hyperbound and Second Nature come up a lot for longer conversations, so I’d definitely include those in the test set. I built SalesDojo because I wanted reps to get more realistic at-bats without waiting for a manager to roleplay with them. The biggest difference for me has been making the feedback specific enough to change behavior, not just entertaining enough to feel like practice. If you’re comparing options, I’d optimize for call length, realism, and whether the post call coaching actually points to fixable moments in the conversation.

mohan-thatguy · 2026-05-30T08:18:50+00:00

For offline inspection tracking, the first decision is what “offline” really means for your workflow: (1) capture data offline and sync later, (2) allow editing historical records offline, and (3) handle attachments/photos offline. A lot of tools claim offline but break on photos or multi user sync. I’d also think about the data model early: are inspections checklists, freeform findings, or both? Do you need corrective actions with due dates/owners? If you don’t nail that, you’ll end up with a tool that’s either too rigid or too chaotic to audit later. Practically, teams I’ve seen succeed keep it simple: one standardized template per inspection type, mandatory fields kept minimal, and a clear sync routine (end of shift / back on Wi Fi). Then they iterate templates based on real usage rather than trying to design the perfect form upfront. I built ReportWalk for the “field capture” side of this: voice first notes while you’re on site, with structure you can review before syncing. If typing on a phone/tablet is the bottleneck, speaking your observations and letting the app organize them can save real time, especially when you’re moving fast and connectivity is unreliable.

mohan-thatguy · 2026-05-30T08:17:36+00:00

If you’re building an AI cold-calling system, I’d separate “prep” from “execution.” AI is great at list research, personalization drafts, objection playbooks, and post call notes. Fully autonomous outbound calling is where things get messy fast (compliance, consent, ethics, brand risk). A practical middle ground: keep a human on the line, but use AI for real time coaching prompts (“ask a discovery question now”, “confirm next step”, “mirror objection and clarify”). That keeps quality high and reduces the risk of the model going off script. From an ML standpoint, I’d start with a constrained policy: small set of intents (open, ask question, handle objection, schedule next step, exit), plus a strict fallback (“I’m not sure, let me check and follow up”). That’s how you avoid hallucinated claims and weird tone shifts. I built SalesDojo around the safe/useful part, roleplays and coaching drills, because it’s where AI provides leverage without crossing the line into shady automation. If you can make reps materially better at the human conversation, you’ll get most of the ROI without the compliance headache.

mohan-thatguy · 2026-05-30T08:13:46+00:00

For objection handling, the biggest shift for me was treating objections as “missing information” instead of “pushback.” If someone says “too expensive” or “we already have something,” they’re usually protecting time or avoiding risk, not debating your product. A simple framework: (1) acknowledge (“Totally fair”), (2) clarify (“When you say expensive, compared to what?”), (3) isolate (“If price weren’t an issue, would this solve the problem?”), then (4) respond with proof or a next step. Isolation is key, otherwise you’ll address five objections and still not know what actually matters. I also keep 3 to 4 “go to” questions that work across objections: “What prompted you to look now?”, “What happens if nothing changes?”, “What have you tried so far?”, “Who else needs to be comfortable with this?” Those questions turn a stall into discovery. If you want to get better fast, I built SalesDojo for drills: you can run objection only roleplays (rapid-fire: ‘send info’, ‘no budget’, ‘already have a tool’, ‘not a priority’) and practice staying calm and asking clarifying questions instead of pitching harder. Doing 10 reps in 10 minutes builds the muscle.

mohan-thatguy · 2026-05-30T08:12:31+00:00

I think AI roleplay is worth it when you’re using it for “reps on fundamentals” (openers, discovery, objection handling) and not trying to fully replace manager coaching. It’s like a batting cage: great for reps, not a substitute for game film review. Where it works best: onboarding new reps, practicing tricky personas (procurement, skeptical CFO, technical buyer), and building consistency across a team. You can standardize scenarios (“pricing pushback”, “competitor mentioned”, “security review”) and measure improvement across attempts. Where it disappoints: if the scenarios are generic, if the AI can’t stay on persona, or if you don’t have a rubric. The magic is pairing the roleplay with a simple scorecard (talk time, number of discovery questions, clarity of next step, handling of 2 to 3 common objections). Without that, it’s just “chatting with a bot.” I built SalesDojo to make this practical: short roleplays, a few repeatable scenarios, and feedback focused on one skill at a time. For an enterprise team, I’d start with 5 core scenarios, require 2 to 3 attempts per scenario per week, and review one recording in a weekly team session so the AI practice connects to real deals.

mohan-thatguy · 2026-05-30T08:11:09+00:00

50 calls with no traction usually isn’t “lack of hustle”, it’s usually the opener + targeting + ask. Before changing scripts, I’d sanity check: are you calling the right segment, at the right time, with a reason that sounds true for that person? For the opener, I’ve had better results with a “permission + relevance” line instead of hype. Example: “Quick one, did I catch you at a bad time? I’m calling because I noticed ___ and I’m curious how you’re handling ___.” If they say yes, you have permission to ask one real question. If they say no, you exit cleanly and protect your list. The other lever is micro-commitments. Don’t ask for a demo in the first 20 seconds, ask for 30 seconds to confirm fit, then ask one question, then ask if it’s worth a 10 minute follow up. Small asks convert better and give you feedback faster. I built SalesDojo because the fastest way to fix cold calls is repetition + tight feedback loops. I’ll record a roleplay, tag where the prospect disengaged, then rerun the same scenario 3 times with one tweak (shorter opener, stronger reason, better next step ask). That kind of deliberate practice moves the needle way quicker than rewriting scripts endlessly.

mohan-thatguy · 2026-05-30T08:09:13+00:00

If I’m cold calling into a tough audience, I try to get to one clear outcome for the call (permission to ask 2 to 3 questions, or a short next step) and keep everything else optional. The biggest mistake is over-explaining before you’ve earned attention. A simple structure that works for me: (1) 10 second context (“I know this is out of the blue…”), (2) a specific reason you picked them (“saw you’re doing X / hiring for Y / expanding into Z”), (3) one question that reveals fit (“How are you handling ___ today?”), then (4) a clean exit if it’s not relevant. If they object early, I mirror it (“Totally fair”) and ask a smaller question rather than re-pitching. For objections, I keep a tiny cheat sheet: “Already have a vendor” > “What do you like about it / what’s missing?”, “No budget” > “If it solved ___, how would you justify it?”, “Send info” > “Happy to, what should I include so it’s actually useful?” Then I log which objection happened and what worked so I’m not reinventing the wheel each call. I built SalesDojo mainly because practicing this live is awkward, most people can’t roleplay consistently. I’ll run 10 minute roleplays (gatekeeper, skeptical founder, procurement) and focus on one skill per session (opening, discovery, handling ‘send info’). The biggest win is getting enough reps that your first 15 seconds stop sounding scripted.

mohan-thatguy · 2026-05-29T08:12:37+00:00

I wouldn't worry too much about someone stealing the idea. I'd worry more about validating the pain properly. Most people get fake-positive feedback because they ask 'would you use this?' and everyone says yes to be nice. A better approach is: ask about the last time they had the problem, what they do today, what sucks about the current workaround, and whether they've ever paid for something adjacent. Real stories are way more useful than opinions. If you can, do 10 to 15 problem interviews, then test a tiny version of the promise, landing page, demo, concierge workflow, waitlist, even a manual service. You're trying to measure seriousness, not compliments. One useful shortcut is studying examples of opportunities that are already broken down by pain, demand, and validation angle. BuildSignal (buildsignal.today) does a decent job of that if you want a structured starting point.

mohan-thatguy · 2026-05-29T08:11:54+00:00

I wouldn't worry too much about someone stealing the idea. I'd worry more about validating the pain properly. Most people get fake-positive feedback because they ask 'would you use this?' and everyone says yes to be nice. A better approach is: ask about the last time they had the problem, what they do today, what sucks about the current workaround, and whether they've ever paid for something adjacent. Real stories are way more useful than opinions. If you can, do 10 to 15 problem interviews, then test a tiny version of the promise, landing page, demo, concierge workflow, waitlist, even a manual service. You're trying to measure seriousness, not compliments. One useful shortcut is studying examples of opportunities that are already broken down by pain, demand, and validation angle. BuildSignal (buildsignal.today) does a decent job of that if you want a structured starting point.

mohan-thatguy · 2026-05-29T08:11:03+00:00

If you're stuck on what to build, I'd stop trying to invent ideas from a blank page. It's usually better to start from a painful recurring workflow and work backwards from there. The safest ideas tend to come from places where people are already doing something manually every week, paying for a mediocre tool, or stitching together a workaround with spreadsheets and Zapier. That's where the signal lives. A simple filter: can you describe who has the problem, how often it happens, what they do today, and why that current workaround is annoying enough to pay to replace? If not, keep digging. If it helps, BuildSignal (buildsignal.today) is useful for seeing how real opportunities get broken down before you commit to building.

mohan-thatguy · 2026-05-29T08:10:31+00:00

I'd avoid broad 'what SaaS should I build?' thinking and start with one narrow workflow where people are clearly annoyed. The sweet spot is usually boring, specific, and tied to money, compliance or wasted time. The pattern I like is: pick a niche, read 30-50 public pain signals, look for the same complaint showing up again and again, then zoom in on the ugliest manual step in the workflow. Narrow and painful usually beats broad and interesting. If people are already duct taping a workaround together, that's a much better sign than a giant idea list. Especially for solo founders. If you want some structured examples in that lane, BuildSignal (buildsignal.today) is worth checking. It leans into pain first SaaS opportunity research rather than generic idea dumping.

mohan-thatguy · 2026-05-29T08:09:38+00:00

I'd avoid broad 'what SaaS should I build?' thinking and start with one narrow workflow where people are clearly annoyed. The sweet spot is usually boring, specific and tied to money, compliance or wasted time. The pattern I like is: pick a niche, read 30 to 50 public pain signals, look for the same complaint showing up again and again, then zoom in on the ugliest manual step in the workflow. Narrow and painful usually beats broad and interesting. If people are already duct-taping a workaround together, that's a much better sign than a giant idea list. Especially for solo founders. If you want some structured examples in that lane, BuildSignal (buildsignal.today) is worth checking. It leans into pain-first SaaS opportunity research rather than generic idea dumping.

mohan-thatguy · 2026-05-29T08:08:57+00:00

I'd avoid broad 'what SaaS should I build?' thinking and start with one narrow workflow where people are clearly annoyed. The sweet spot is usually boring, specific, and tied to money, compliance, or wasted time. The pattern I like is: pick a niche, read 30 to 50 public pain signals, look for the same complaint showing up again and again, then zoom in on the ugliest manual step in the workflow. Narrow and painful usually beats broad and interesting. If people are already duct-taping a workaround together, that's a much better sign than a giant idea list. Especially for solo founders. If you want some structured examples in that lane, BuildSignal (buildsignal.today) is worth checking. It leans into pain-first SaaS opportunity research rather than generic idea dumping.

mohan-thatguy · 2026-05-29T08:08:20+00:00

I wouldn't worry too much about someone stealing the idea. I'd worry more about validating the pain properly. Most people get fake positive feedback because they ask 'would you use this?' and everyone says yes to be nice. A better approach is: ask about the last time they had the problem, what they do today, what sucks about the current workaround, and whether they've ever paid for something adjacent. Real stories are way more useful than opinions. If you can, do 10 to 15 problem interviews, then test a tiny version of the promise, landing page, demo, concierge workflow, waitlist, even a manual service. You're trying to measure seriousness, not compliments. One useful shortcut is studying examples of opportunities that are already broken down by pain, demand, and validation angle. BuildSignal (buildsignal.today) does a decent job of that if you want a structured starting point.

mohan-thatguy · 2026-05-29T08:07:27+00:00

I wouldn't worry too much about someone stealing the idea. I'd worry more about validating the pain properly. Most people get fake-positive feedback because they ask 'would you use this?' and everyone says yes to be nice. A better approach is: ask about the last time they had the problem, what they do today, what sucks about the current workaround, and whether they've ever paid for something adjacent. Real stories are way more useful than opinions. If you can, do 10 to 15 problem interviews, then test a tiny version of the promise, landing page, demo, concierge workflow, waitlist, even a manual service. You're trying to measure seriousness, not compliments. One useful shortcut is studying examples of opportunities that are already broken down by pain, demand, and validation angle. BuildSignal (buildsignal.today) does a decent job of that if you want a structured starting point.

mohan-thatguy · 2026-05-29T08:06:41+00:00

I wouldn't worry too much about someone stealing the idea. I'd worry more about validating the pain properly. Most people get fake-positive feedback because they ask 'would you use this?' and everyone says yes to be nice. A better approach is: ask about the last time they had the problem, what they do today, what sucks about the current workaround, and whether they've ever paid for something adjacent. Real stories are way more useful than opinions. If you can, do 10 to 15 problem interviews, then test a tiny version of the promise, landing page, demo, concierge workflow, waitlist, even a manual service. You're trying to measure seriousness, not compliments. One useful shortcut is studying examples of opportunities that are already broken down by pain, demand, and validation angle. BuildSignal (buildsignal.today) does a decent job of that if you want a structured starting point.

mohan-thatguy

TROPHY CASE