Back to podcasts

Keep, fix, or ditch QuickBooks? A contractor’s reality check

QuickBooks powers the accounting for a huge share of construction businesses, but as contractors grow, many start asking the same question: is QuickBooks still the right fit, or is it time to move on?

In this episode of The Cost Codes Show, Ryan Gilmore sits down with Scott Franchini, partner at Red Hammer and a specialist in construction accounting, job costing, and technology strategy, to unpack what’s really behind that question. Scott explains why many contractors have not actually outgrown QuickBooks, but instead run into issues caused by poor setup, the wrong subscription tier, weak job costing structure, or disconnected workflows. He also breaks down the tradeoffs between staying on QuickBooks, moving to a mid-tier construction accounting platform, or jumping to a larger cloud ERP.

The conversation goes beyond software features and gets into what really drives better decisions: clean data, strong reporting, scalable processes, and a technology stack built around the way a contractor actually operates. Scott also shares how specialty contractors can often get the best of both worlds by keeping QuickBooks as their accounting backbone while layering on purpose-built tools for budgeting, commitments, billing, project controls, and field operations.

If you’re a growing contractor or an accountant advising construction clients, this episode offers a practical framework for evaluating your current systems, understanding where QuickBooks falls short, and deciding what kind of investment will actually support the next stage of growth.

Want to go deeper on construction accounting, ERPs, and tech stack decisions? Scott Franchini’s in-depth articles break down these topics with unmatched clarity and real-world experience:

https://www.redhammer.io/blog/before-you-ditch-qbo-a-clear-look-at-the-construction-software-gap

https://www.redhammer.io/blog/the-complete-guide-to-intuit-enterprise-suite-for-construction-companies-2025

https://www.redhammer.io/blog/best-construction-accounting-software-platforms-in-2025-complete-guide-for-contractors

Resources & Takeaways

  • Most contractors have not outgrown QuickBooks itself; they have outgrown a poor setup, weak job costing structure, or disconnected processes.
  • Mid-tier construction accounting systems can improve native job costing, but often create new problems around usability, integrations, automation, and back-office efficiency.
  • The strongest technology decisions start with documented business requirements, future growth plans, and operational pain points, not frustration with current software.
  • For many specialty contractors, pairing QuickBooks with purpose-built construction tools can deliver better control, reporting, and scalability without a full ERP migration.
  • The real return on technology investment comes from more accurate, timely data and better visibility into job performance, not just software cost savings.

Watch

Listen

Read Transcript

Ryan Gilmore: Hello everyone, and welcome to The Cost Codes Show, presented by Knowify. This is a podcast where we focus on helping trade contractors run and grow their businesses.

Today I’m excited to be joined by Scott Franchini. He’s a construction accounting and construction technology expert, as well as a partner at Red Hammer, an accounting firm specializing in construction accounting and financial management.

Scott has a ton of experience helping contractors choose the right technology and tools for their workflows and businesses, and he’s going to share that with us today.

How are we doing today, Scott?

Scott Franchini: We’re doing great, Ryan. Thanks for having me.

Ryan Gilmore: Awesome. Excited to have you on.

Scott, to kick things off, for folks who don’t know you yet, maybe you could talk a little bit about your background, the kind of work you do, and how you got to where you are today with Red Hammer.

Scott Franchini: Yeah, I appreciate that.

I’m Scott Franchini, and I’m a partner at Red Hammer. We’re an outsourced accounting company that specializes in the construction industry. Our clients are subcontractors, developers, and general contractors, typically with revenue from zero to $30 million, so we sit really nicely in the small- to medium-sized business range.

We perform controller-down accounting services. With our team-based approach, we can come in and do things like AP, help with payroll, and ultimately, because we’re job cost experts, help clients not only generate but also review their financial statements and work in progress.

One of the things that really separates us from our competition is that we’re not just what we call bookkeepers. We’re highly technical. In every case where we’re bringing on new clients, we’re looking at system configuration, system integration, and data quality.

More often than not, we’re going back, resolving issues, fixing things, and getting clients up to speed before we can actually come in and do the accounting services.

My background, interestingly enough, is not originally on the construction accounting side. I started my career at Deloitte back in 1999. I was focused on ERP implementations, particularly JD Edwards, in the construction, manufacturing, and distribution spaces. Later, I worked for Microsoft and then started my own systems integration company.

So I have a deep background in software implementations, data cleanup, and migrations for billion-dollar companies. When I came over to Red Hammer—which was actually started in 2011 by one of my former colleagues from Deloitte—I joined in 2020. Our goal was to take a company that had been serving the Hawaii community and expand it to the continental United States.

Now, here we are five years later. We’re in 20 different states and serve about 130 contractors across the nation.

Ryan Gilmore: That’s awesome. Very impressive momentum over the past five years or so.

That’s also a really good transition to what we’re going to focus on today, which is the construction tech stack, with QuickBooks Online maybe as the centerpiece.

It’s one of the most popular accounting softwares out there. Knowify has a really strong integration with QuickBooks, and the vast majority—if not all—of our clients are using it. We really want to help contractors understand: When is QuickBooks enough? When is it not enough? What solutions are out there that can help you build on QuickBooks to create your ideal tech stack? And where does some of the newer stuff that Intuit has released—like Intuit Enterprise Suite, or IES—fit into the equation?

So maybe we could get started there. When a contractor comes to you and says, “We’ve outgrown QuickBooks Online,” what do you look at first? How do you handle that question?

Scott Franchini: I think it’s usually driven by a couple of reasons.

One is that they don’t know what they don’t know. Oftentimes, the system is just not set up or configured correctly. So the first thing we do is ask for the keys to the car. If we can’t look under the hood, we can’t provide suitable feedback.

And when I say often, I mean seven or eight times out of ten, the system configuration is not correct. Within five minutes, I can usually tell if they’re utilizing the functionality available in the version they’re on, whether certain features are turned on or off, and within 15 minutes I can usually tell if they’re using it correctly.

We have an assessment process we go through. Ultimately, when you start getting into job costing, companies need to have a certain tolerance for what they’re capable of doing. You can get really detailed, so we talk with them about their goals and what they’re trying to achieve.

Usually, we can come in and say, “Okay, these are the things you need to do in order to get your desired result,” and from there you can get the reporting you want. But if you don’t set it up right, you’re not going to maximize the true value of the software.

Ryan Gilmore: Let’s dig into that a little bit. In your experience, what are some of the common setup mistakes you see—whether in job costing or other parts of the contractor workflow?

Scott Franchini: First, a lot of companies are on the wrong version.

For example, if they’re using QuickBooks Plus, they’re limited to a small number of reports, and none of them are really strong job cost reports. You can look at a profitability report by project, but it’s not until you get to Advanced that you start to expand into more reporting—things like estimate versus actual, WIP, and so on. Then if you go to IES, you get even more detailed reporting.

So if they’re on Plus, we already know they’re not looking at job costs in the right way.

But once they’re in Advanced, the number one issue we see is the cost code structure. Oftentimes, instead of creating products or items that function as logical cost codes relative to their budget lines, they embed them into the chart of accounts or use classes—which is a definite no-go for this purpose.

We run into that all the time. You have to use products because all of the job costing reports in QuickBooks rely on those products being used correctly. If you’re trying to do an estimate or a budget, you need to put it in using those cost codes.

At the contract level, you still need products—it’s a schedule of values versus budgetary codes—but then you also have to job cost at the project level. Once you do that, it opens up a whole set of functionality and reporting, including estimate-to-actual comparisons and more effective use of the platform.

Ryan Gilmore: That’s really helpful—especially understanding the different versions, what you get from them, and where the setup pitfalls are.

So we’ve talked about setup issues. In your experience, what causes contractors in their day-to-day operations to think they might need to move off QuickBooks? What specific pain points make them feel like QuickBooks is no longer enough and that they need an ERP or another system?

Scott Franchini: What we see a lot is that companies reach a certain point in their business—usually around the $5 million mark—and think, “I’ve graduated. I need to get onto something more sophisticated. I need all this additional job costing. I hired a new project manager and he used Foundation, and Foundation is supposed to be amazing. My wife isn’t doing the books anymore.”

It’s a mix of excitement, growth, and new ideas.

Now combine that with the fact that they’re not set up correctly in QuickBooks and aren’t even doing what’s necessary to do good job costing inside the platform. So often they’re chasing a carrot. And what we want to do is paint the picture of what chasing that carrot really looks like.

I’ll say this: products like Foundation and Sage do have better native job cost functionality. But the tradeoff is that you go completely backward from a technology perspective, and you lose a ton of efficiency.

In QuickBooks, you can quickly go in, change things, recode items, and move fast. You lose a lot of that in some of these other systems. So yes, Sage and Foundation have strong job costing functionality—especially around things like AIA billing, commitment control, and more advanced payroll job costing. One of the deficiencies in QuickBooks right now is that you can’t really job cost QuickBooks Payroll the same way.

But that added functionality comes with other pains. So it becomes a matter of picking your poison—or taking QuickBooks and layering on third-party applications so you can maintain the flexibility, accessibility, and usability of QuickBooks while adding the missing pieces.

Ryan Gilmore: That makes a lot of sense. You get strong native functionality in some of those other platforms, but the underlying technology can be older or less modern. It can also be harder to add new tools, connect new software, or use the system from a browser.

So with that in mind, what are some of the areas where QuickBooks falls short and where you’d start looking for other tools to plug the gaps?

Scott Franchini: One of the first places we see companies wanting something additional is contract management and AIA billing.

If you’re in QuickBooks today, you’re usually handling those things in spreadsheets or another third-party tool, then transposing the data back into the system. That’s a pretty big deal. In a percentage-of-completion environment, you want to be able to track that stuff and look at everything from a rolled-up cost perspective.

When you’re doing that in Excel, you’re basically trying to converge data from two different systems, and that’s often not good—especially for the project management side.

QuickBooks is really perceived as an accounting system, not a project management system. When you move into some of these more construction-oriented applications, they’re perceived as more of a combined environment. So when you start thinking about billing and project management, it’s much better if that’s all in one ecosystem—or at least interconnected.

Ryan Gilmore: Do you have any war stories—cases where a contractor was thinking about moving to a larger ERP and you were able to help them avoid a bad decision or solve the problem by building a better QuickBooks-centered stack?

Scott Franchini: I don’t think we’ve ever fully stopped somebody once they’ve started down that path. Usually by that point they’ve already invested in it and have money committed, so they’re going to see it through.

But we have had clients recently who are on Foundation and are looking to move back—likely to IES. And what it comes down to is exactly what I mentioned earlier: they say, “The job costing is great. I can set up my jobs, schedule of values, budgets, and restrictions. I can get great WIP reporting and job cost reporting.”

But then they say, “I have to extract bank transactions from the bank every month and import them through a CSV. I have to manually create a 200-line journal entry. I have to enter each credit card transaction, each AP transaction. If something gets rejected, I have to re-enter it.”

It’s the back-office pain and inefficiency that drives them insane. It’s unforgiving.

And beyond that, we’re in an era where RESTful APIs are the norm. AI is growing rapidly. Companies want interoperability and modern integrations. When you’re on an old non-SaaS platform—or a hosted environment that’s really just remote desktop—that’s not the same as true cloud software. Those systems don’t have the interconnectivity or open APIs you need, and that becomes restrictive.

People get excited about new technology and then find out the system simply can’t support it. That’s where a lot of frustration comes from.

Ryan Gilmore: That’s really helpful.

So for a contractor in the $6 million to $10 million range, what does a healthy QuickBooks-centered tech stack look like? Let’s say they’re a commercial contractor—maybe mechanical, electrical, or plumbing.

Scott Franchini: If they’re a GC, there are other software applications and third parties we might recommend that are better aligned with that environment.

But for specialty subs—and even on the service side—that’s really where we like to recommend Knowify.

The reason is that we can take the QuickBooks environment, whether it’s QuickBooks Online or IES, and layer Knowify on top of it. We look at it in stages.

First is job setup and management. You can control the contract from the very beginning with the different options available. The next layer is budgeting. From the budget, you can create commitments and tie those together. Then from the budget, you can also create the schedule of values, which turns into your AIA billing.

So all of these things that we can’t really do on the QuickBooks side, we can do on the Knowify side.

The other thing I love about Knowify is control. That’s something QuickBooks is not great at. In Knowify, we can create restrictions that only allow certain things to be costed based on budget items. On the QuickBooks side, if I’m costing something from a bank feed, I see everything. It doesn’t cascade based on the project I chose. Those restrictions are really helpful for maintaining clean data.

From there, we can generate job cost reports, WIP, and everything else within Knowify. And the field service side is also great. If they’re a mechanical or plumbing business and have a service component, service orders provide a lean way to job cost without having to go into all the intricacies of a full project job cost environment.

One of the things customers really love is the time feature—everything in one place, where they can go out, do the work, attach expenses, do the billing, and manage it all from a single portal.

Ryan Gilmore: When you’re bringing on a new client—or helping an existing client revamp their tech stack—do you have a checklist or a set of questions you go through?

Scott Franchini: We don’t really have a checklist. I think part of that is because I’ve been doing this so long that I work off the responses they give. If I wrote up a script and handed it to someone else, they could follow it, but they wouldn’t do it the way I do.

Our process really starts with understanding pain points. What issues are they seeing? That could be software-related, people-related, growth-related, or something else entirely. Once we understand the pain points, we can start turning that into a future-state vision.

A lot of people get clouded by the immediate problem and want to solve only that. But anytime you’re implementing software, you have to step back and ask:

  • Does this solve the problem I have right now?
  • How does it work for the rest of the organization?
  • How does it affect other departments?
  • What do I need three years from now?
  • What do I need five years from now?
  • Is this product scalable?

If I’m going from $10 million to $20 million, do I need to change software again in a year?

That’s part of what we do: help them define current pain points, future requirements, and what they actually need.

And honestly, one of the biggest mistakes companies make is thinking they need to do everything at once. These things can be phased. We want to move slowly and methodically.

I’m a firm believer that whenever you introduce technology, you have to look at it from a people, process, and technology perspective. If you focus only on the technology and ignore process, change management, and having the right people in place, you’re not going to be successful.

A lot of times, the “system problem” is actually a people problem. You can move from System A to System B and still have the same issues if the people and process side doesn’t change.

Ryan Gilmore: That’s a really holistic approach, which I definitely appreciate.

Let’s say a contractor comes to you with a defined budget—maybe $50,000 to $100,000—that they want to invest in their business to grow over the next couple of years. Where would you rather see them put that money? Into new software? Better configuration of their existing software? Or more on the people and process side?

Scott Franchini: It’s definitely a loaded question, and it depends on the business, where they are, and where they realistically see themselves going.

Everybody says they want to double, but we can usually tell pretty quickly from the books and the backlog whether that’s realistic.

It really comes back to understanding current issues, where they want to be, what the business complexity looks like, and what the future state is.

A good example: we’re working with a company here in Phoenix that does flooring. Their business model is complicated because they work with a lot of GSA and government-related entities, so taxation is complex. They also do a lot of materials work, which means inventory requirements. That is not a good fit for QuickBooks. It’s not a good fit for QuickBooks and Knowify, or QuickBooks and Buildertrend, either. They need a more advanced ERP like NetSuite or Acumatica.

When you start talking about complex business models, multi-location operations, layered departments, inventory, or workflow requirements, that’s when you need to step back and think more seriously about a higher-end platform.

Volume matters too. We had an electrical contractor years ago that was growing rapidly and needed a more enterprise-level system to support the scale and integrations they needed.

But if you’re talking about a $50,000 to $70,000 investment over five years, that’s not actually a huge software budget. I would not tell them to go to the middle-tier software applications. I think that’s going backward. They’ll pay for onboarding, they’ll spend money to move, and then they’ll likely be unhappy in a couple of years because the technology won’t keep pace.

I’d tell them to be patient. Use QuickBooks as the baseline, add third-party applications like Knowify, Procore, or Buildertrend where appropriate, and build the business around that before you go spend hundreds of thousands of dollars on NetSuite, Intacct, or something similar.

Ryan Gilmore: You touched on something I’d love to dig into a bit more: the tradeoffs between QuickBooks, those middle-tier platforms, and full-scale cloud ERPs.

Scott Franchini: I’ll explain it in a simple way.

I think about it in two dimensions: functionality and technology.

From a functionality perspective, let’s look at three tiers:

  • Tier 1: QuickBooks and IES
  • Tier 2: Foundation, Sage 100, Sage 300, Spectrum, Vista, and maybe CMiC at the top end
  • Tier 3: NetSuite, Acumatica, Intacct, and similar cloud ERPs

On the QuickBooks side, you have low-to-mid job costing functionality. You can do job costing, but it’s not highly restrictive or controlled. People can do things in too many different ways.

The middle tier gives you the strongest native job costing functionality. Those companies have been in the business for decades and have built entire systems around the needs of contractors. They really nail that part.

Then on the top tier—NetSuite, Acumatica, Intacct—you get above-average job costing, but often not as strong as the middle tier. In some cases, like NetSuite, you still need third-party tools to really maximize it.

So functionally, the middle tier is the peak.

But now look at the technology side.

QuickBooks is very strong technologically. Tons of APIs, a huge marketplace, open documentation, great interoperability, great Zapier support—it’s very modern.

Then you move to the middle tier, and that drops hard. Many of those systems are remote desktop or client-server environments. They either don’t have APIs or the APIs are highly restricted. You’re dealing with ODBC connections, special processes, more maintenance, and systems that just aren’t true SaaS platforms.

Then at the top tier, the technology gets strong again. NetSuite, Acumatica, and similar platforms have good APIs, good marketplaces, and a lot of flexibility if you have developers or implementation support behind you.

So on the technology side, it’s more of a reverse bell curve.

That’s why I think it’s so useful to look at total cost of ownership. If I start with QuickBooks and then add a third-party system like Knowify, I can dramatically increase functionality without sacrificing the technology benefits—and I can do it at a much lower cost.

If I go into something like Foundation or Sage 300, I may be paying $2,000 to $3,000 a month in licensing, plus implementation costs, while also going backward on the technology side.

If I jump to the top tier, now I’m talking about at least $100,000 to implement—and I’ve seen contracts go to $250,000 or $300,000—with licensing between $3,000 and $10,000 a month.

So the question becomes: how much complexity do you really have, and do you actually need that jump?

We have a general contractor running QuickBooks at $100 million. We have a new client moving from desktop to IES at $60 million as a specialty subcontractor. So we know it can work if it’s set up correctly and the functionality is fully utilized.

Ryan Gilmore: That was a great explanation. I especially like the reverse bell curve visual.

Where would you put IES on that spectrum? It’s still the new kid on the block, so I think a lot of people are trying to figure out where it fits.

Scott Franchini: The one thing I love about Intuit right now is how rapidly they’re investing in the future of the platform. And not just in IES itself, but in things like agentic AI and the broader future of the ecosystem.

At its core, IES is different from QuickBooks because it supports multi-entity. In QuickBooks Online, if you have three or five entities, you’re basically running separate QBO files and managing intercompany manually. That’s painful. IES is fantastic for multi-entity rollups, consolidations, and intercompany transactions.

That’s a big deal, because one of the primary reasons companies move to something like Intacct or NetSuite is that they need that multi-entity capability.

The other thing Intuit has added is dimensions, which I think of as advanced classes. They let you look at your business—especially the P&L—in different ways. You might want to look at location, service lines, business units, or assets. That’s powerful.

We do need to be careful on the job costing side not to create extra coding just for the sake of coding, but dimensions are a major enhancement.

And beyond that, IES is clearly growing in construction functionality. There are something like 11 new reports compared to standard QuickBooks, including good reports that people actually ask for, like committed cost reporting. They now have change orders and budgets, and Intuit has announced a dedicated construction edition.

So I know they’re committed to it. I’ve had multiple conversations with Intuit, and I believe they’re paving a really solid path.

When you see a company investing in the platform and in the future of technology, that’s the kind of company you want to align yourself with. It shows they care about what the future looks like.

That’s why for a lot of customers I’m saying: be patient. Don’t spend hundreds of thousands of dollars jumping to something else that’s going to take nine months to implement and still may not deliver what you want. Stay focused on all the things QuickBooks does well and watch where IES is going.

There are so many things people like about QuickBooks that they don’t appreciate until they’re gone—bank feeds are a perfect example.

Ryan Gilmore: That’s a great point. When you’re choosing the software that’s going to be central to your business, seeing a clear product roadmap and active investment definitely matters.

You mentioned bank feeds as one of those things people miss when they’re gone. Are there any other examples of features or qualities in QuickBooks that people don’t fully appreciate until they lose them?

Scott Franchini: Yes—quite a few, actually.

I usually talk about four characteristics that QuickBooks Online has that a lot of other systems don’t: usability, adaptability, flexibility, and interoperability.

  • Usability: The interface is intuitive. The menu structure is simple. The search function is excellent.
  • Interoperability: We’ve talked about this throughout the conversation—APIs, integrations, and connected tools.
  • Flexibility: The ability to create reports on the fly, export data into Excel, and work quickly.
  • Adaptability: There are a lot of people out there who know QuickBooks. Try finding accountants or team members who know Foundation or Sage well. That’s harder.

One of my favorite QuickBooks features is Spreadsheet Sync. Once you get to QuickBooks Advanced, Spreadsheet Sync is amazing. It allows us to pull data into Excel, make changes, and sync it back. It lets us load data quickly without building a bunch of import files, and it saves us from a ton of manual data entry.

There are some restrictions, of course—you can’t mass-delete everything—but that’s fine. Overall, it’s an incredibly powerful tool.

And on the talent side, we’re dealing with a profession that is aging. More people are leaving than entering. The younger workforce doesn’t want to work in archaic software. They want modern systems, AI capabilities, speed, and efficiency.

I think companies forget how much those things matter until they move to something older and more rigid.

Ryan Gilmore: We’re getting toward the end of the interview, so I wanted to finish with two questions.

First, we’ve talked a lot about investing in technology, but the other side of investment is understanding the return on that investment. How do you help business owners think about the ROI of their technology investments?

Scott Franchini: That’s a great question.

One of the things we used to say at Deloitte and Microsoft was: never sell an ERP package based on ROI. The reason is that the realization of ROI is a long game, not a short game.

There’s a misconception that you can just plug in a new system and suddenly profitability goes up. It doesn’t work like that.

Again, it has to be people, process, and technology. If you’re not willing to do everything required on all three fronts, your ability to realize ROI drops dramatically.

I’ve seen plenty of situations where companies say, “We’re going to bring in this new software, but we want to keep doing things the same way, and Mary Jane is going to manage it.” And the reality is that the issue wasn’t the software—it was the process.

So when I talk to business owners, I don’t like talking about ROI in purely dollar terms. I like to talk about it in terms of data and visibility.

The real value is in creating:

  • more accurate data
  • more timely data
  • better metrics you can actually react to

That’s where the payoff comes from.

I can’t tell you how many companies we work with that don’t run a WIP properly, and it’s a tragedy. They think they know what’s happening on their jobs, but they don’t really know where they stand in terms of gain or fade, overbilling or underbilling, or month-to-month performance.

That lack of visibility can absolutely hurt profitability and create tax consequences at year-end.

So to me, the best ROI is having a pulse on the basics and the ability to react. I’d much rather frame it that way than promise a business owner that if they spend $10,000, they’ll save $15,000.

Ryan Gilmore: I love that. I think that framing is a lot more tangible and easier to wrap your head around.

Last question: We always like to end The Cost Codes Show on an action-oriented note. If there’s a contractor listening who wants to make one positive change to their tech stack this week, this month, or before the end of the year, what would you recommend they do?

Scott Franchini: The first thing I always tell people is: do the research.

We’re in a world where there’s a ton of information and a ton of AI available. Use multiple platforms. Search. Learn.

But when you’re evaluating technology, don’t just look at it from the perspective of your current pain. You have to look at it in the context of your entire business.

One of the first questions I ask is: Do you know your requirements?

And by that I mean: have you actually written them down? Have you worked with your organization and different departments to document what you have to have, what you want to have, what you think you need, and what you really don’t need? Have you also documented what those requirements look like next year, and three years from now?

That exercise alone—putting requirements down on paper, evaluating them, and scoring them—is probably one of the best things any company can do.

Because once you’ve done that, you can start aligning those requirements with what different software applications can actually do. That helps you understand:

  • functionality gaps
  • technology gaps
  • reporting gaps

And those things are often ignored.

That process helps shape the path forward. Maybe it confirms that staying in QuickBooks is the right move. Maybe it reveals that you really do need to move to NetSuite because of specific requirements.

But the key is: research, document the requirements, and then talk to multiple software companies. Don’t just talk to one.

Figure out the best fit. If you do that initial assessment well and spend adequate time on it, you’ll save yourself an enormous amount of pain, time, and money.

Ryan Gilmore: I love it. Very practical advice.

Scott, thank you for joining us today. Where can folks learn more about Red Hammer if they’re interested in your services?

Scott Franchini: Sure. You can go to our website at www.redhammer.io.

We’ve got our service pages there, and we also do a lot of blogging—real, substantive blogging, not just SEO content. The articles are very purposeful and can help people better understand the implementation process.

I also have a full article on the software gap we discussed today. And if someone is interested in learning more about IES, we have what I believe is the most comprehensive article on the web related to IES. It’s updated constantly.

We also built an IES bot where you can go in and ask questions, compare desktop to online to IES, and get guidance based on the type of contractor you are and what you’re looking for.

We’re also on LinkedIn, so feel free to connect with me there. And if you want help, we’re happy to sit down, do an assessment, and help pave a path for the future.

Ryan Gilmore: I’ll echo Scott’s words—the articles he’s written are incredibly comprehensive and thorough. As someone who works at Knowify but isn’t a construction company owner, and doesn’t help implement full tech stacks every day, they really helped me understand the landscape.

We’ll link some of those articles in the show notes for this episode.

Thanks again, Scott, for joining us. If you need help managing your construction projects or your finances, please visit Knowify at Knowify.com. We’d love to help.

Thanks for tuning in, and we’ll be back soon with another episode.

Related Resources