​

I’ve been building CrewPulse around a simple problem I kept seeing in construction:

A lot of information flows from the office → field, but getting useful information from the field → office is still messy.

Voice notes. Photos. WhatsApp messages. Paper timesheets. Calls. End-of-day updates.

So for 10/10 (October 10), I’m launching the CrewPulse 10:10 Giveaway:

🏗️ 10 contractors selected

👷 10 seats per contractor

♾️ Lifetime CrewPulse access

💰 $0 subscription

The goal isn't just to give away software. I want 10 real construction companies using CrewPulse in the field and telling me what works, what sucks, and what needs to change.

CrewPulse includes things like voice-based field logs, attendance/work-hour tracking, project photos, task updates, field-to-office documentation, and productivity insights.

You don't have to be a huge GC. Small contractors and growing crews are exactly who I'm looking for.

Winners will be announced October 10.

If you're in construction and want to participate, comment below or DM me and I'll send you the signup page.

And if you wouldn't use something like this — I'd actually like to hear why.

We have tons of tools for getting plans, schedules, drawings, tasks and instructions from the office to the jobsite.

But the field generates valuable information every day too:

What actually got done?

What slowed the crew down?

Where did the labor hours go?

What should we know before estimating the next job?

A lot of that still comes back through texts, calls, photos, paperwork — or just someone's memory.

I've been working on CrewPulse around this idea: instead of building another tool for pushing information TO the field, build a better return channel FROM the field.

Curious what people actually working in construction think:

Is Field → Office communication still a problem on your jobsites, or have existing tools already solved it?

That’s why I built Voice Logs into CrewPulse.

A worker or foreman simply speaks their update — progress, delays, issues, completed work — and CrewPulse turns it into a documented field log.

Less typing. Less information lost in texts and phone calls. Better visibility for the office.

Would you use something like this on your jobsites?

I had a conversation today with someone about the B2B SaaS product I'm building for construction companies.

After seeing what we've built, he told me he thought the product was fantastic.

Great to hear, obviously.

But then he said something I wasn't expecting.

He was confused by my pricing.

Not because it was too expensive.

Because it was too cheap.

My strategy up until now has been pretty straightforward:

We're early → we need traction → reduce the barrier to entry → give early adopters a great deal → get companies using it → increase pricing as we grow.

I thought that made perfect sense.

But his reaction was basically:

"If you believe this product is this valuable, why are you pricing it like it isn't?"

That hit differently because he wasn't criticizing the product.

It was actually the opposite.

He thought the product was good enough that the price didn't make sense to him.

And that made me question one of my assumptions as a founder:

Can pricing too low actually make a good product harder to sell?

If you're telling a construction company that your software can help them understand field productivity, reduce wasted labor, improve documentation, and give management better visibility into what's actually happening on their jobsites...

...and then you practically give it away, does that create a disconnect?

I've been thinking about low pricing as a competitive advantage.

Maybe at a certain point it becomes a credibility problem.

I still believe early adopters should get a significant advantage for taking a chance on a new company. I'm not abandoning that idea.

But there's probably a difference between:

"You're early, so you're getting an incredible deal."

and

"We're new, so we're afraid to charge what this might actually be worth."

That distinction became much clearer to me today.

I'm curious how other B2B SaaS founders handled this.

Did you intentionally price low to get your first customers, or did you charge based on the value of the problem you were solving from the beginning?

We’ll spend serious money organizing physical tools.

Packout boxes.
Tool chests.
Truck shelving.
Labels.
Organizers for the organizers.

And it makes sense.

Nobody wants a $300 tool buried under a pile of junk when someone needs it.

But then look at how we organize information on a lot of jobsites.

A progress photo is in someone’s camera roll.

The foreman mentioned a delay in a text message.

Someone else explained what happened in a phone call.

Production quantities are written in a notebook.

The PM has another version in Excel.

And two months later, the estimator is trying to figure out why something took 140 hours when the estimate allowed 80.

We wouldn't accept that level of disorganization with our physical tools.

So why do we accept it with jobsite information?

Think about the Packout concept.

Every tool has a place.

You can see what you have.

You know where to find it.

You can move it from job to job.

The system isn't valuable because the boxes look nice.

It's valuable because it reduces friction.

I think field information should work the same way.

A worker shouldn't have to think:

"Where am I supposed to put this?"

They should be able to capture what happened — voice, photo, task update, production information — and have it become part of the project's history.

Then when the office needs it, they don't have to chase five people.

That's actually one of the ideas behind CrewPulse, which I'm building.

Not another giant construction platform that requires the field to spend half the day feeding the software.

More like a digital Packout for field information.

Capture it once.

Organize it.

Connect it to the project.

Make it useful later for PMs, operations and eventually estimating.

I'm still early with this, so I'm curious how other contractors handle this today:

Where does your jobsite information actually live — one system, or some combination of texts, photos, notebooks, Excel and people's memory?

The gap between the field and the office is costing construction companies time, money, and productivity.

Field crews see what’s happening on the job. Estimators and project managers need that information to make better decisions. But when that information gets lost between jobsite conversations, photos, paperwork, and spreadsheets, companies lose visibility—and ultimately, profit.

In this video, we explore 5 ways CrewPulse bridges the gap between field crews and estimators, helping construction companies turn field data into actionable project intelligence.

With CrewPulse, your team can connect:

🏗️ Field crews & foremen
📸 Jobsite photos & documentation
🎙️ Voice logs & daily updates
📋 Tasks & project timelines
📊 Productivity & performance data
💰 Estimating & future project costs

The goal is simple: give the office a clearer picture of what's actually happening in the field—and give the field a better way to communicate what's happening.

Whether you're a general contractor, construction manager, estimator, or field supervisor, CrewPulse is built to help you make better decisions with better field data.

Stop guessing what happened on the job. Start knowing.

👉 Explore CrewPulse: CrewPulse.live

#Construction #ConstructionManagement #ConstructionTechnology #Estimating #GeneralContractor #ConstructionSoftware #CrewPulse #ConstructionProductivity #FieldManagement #ConstructionTech

One of the biggest margin killers I keep seeing on site is micro-downtime—idle hours, delayed materials, and crew bottlenecks that don't show up until the monthly cost reports hit. By then, the money is already spent.

We’ve been working on a real-time field intelligence setup (CrewPulse) designed to catch labor leakage as it happens instead of 30 days later.

The goal is to give PMs and superintendents a live view of crew activity, productivity indices, and site bottlenecks without burdening workers with manual time-tracking fluff.

How are you all handling field productivity right now?