Back to the blog
BUILDING ROSS CORE IT

How Did I Build the Business Behind Ross Core IT?

When I started Ross Core IT, the idea was pretty simple: build a website. Then I kept digging. Once I understood the difference between business management and service operations, I settled on four layers meant to keep my services, prices, quotes and job records from drifting apart.

How did a simple website turn into a bigger project?

I started teaching myself website design and search visibility: how a site shows up in Google and in AI answers (SEO, AEO, GEO, and schema). Somewhere along the way, I came across the idea of establishing a hierarchy within a business niche. In plain English, that meant becoming the go-to name for one specific thing, so that when people search for that topic, that site would be the one that shows up as the expert.

Naturally, that sent me down another rabbit hole.

I started learning how to audit websites. Then I started looking harder at how the business itself was organized.

At first, I was mostly using one AI tool. Eventually, I was using three or four on a task: researching, comparing answers, building things, and checking the results.

I was assigning overnight tasks to Codex, an AI coding tool, involving labs, virtual machines, recordings, and content workflows, then checking the results. Then I started digging further into automation.

Why wasn't an organized file system enough?

Before I really stopped to look at it, I had accumulated around 20 automation tools, a website, and a growing pile of service documents and contracts.

Every time I came up with a service idea, I created another PDF to keep it organized.

My Windows filesystem was mostly organized.

Or so I thought.

I knew where a lot of the files belonged. What I hadn't fully worked out was how all those files, services, and applications were supposed to relate to each other.

How did I start learning the business side?

Throughout this process, a lot of the people I tried talking to about what I was building didn't seem particularly interested.

I started studying business management: the concepts, strategy, frameworks, hierarchy, processes, and systems, and how they work together.

Every time I developed a service concept, I started analyzing it against what I was learning. That helped, but it also created more material to manage.

I had tools. I had documents. I had ideas for services.

I didn't have money sitting around for a lawyer or a marketing budget. I was trying to build the business while learning how to run it.

What's the difference between business management and service operations?

Eventually, I came across the term "service operations." That helped me put a name to the distinction I had been trying to understand.

The way I came to understand it, business management sets the direction, rules, and boundaries of the company. Service operations takes a customer's job through those boundaries without reinventing the process every time.

That was when organizing the business started to mean more than organizing folders. I go into this distinction in more detail in the four layers that keep prices and quotes from drifting.

What are the four layers that keep my business organized?

I decided on a four-layer structure and saved it as a reusable skeleton.

  • Owner Development and Strategy. This is where I keep the operating standards, playbooks, business concepts, and rules I use to make decisions. It helps me work out how I want the business to run. My generators never read from this layer directly.
  • The Commercial Master. This holds the approved service descriptions, prices, scope boundaries, and editable document sources. I wanted one authoritative place for that information. If I change a price or update a service, I need to know which version is current. I also need to know which version was used for an older quote.
  • Generators and Software Applications. These are the tools that use the approved information. My proposal builder and web-based client/server manager belong here. I didn't want each application maintaining its own separate copy of my prices and business wording. That would give me more places to update and more opportunities for things to drift apart.
  • Client and Job Records. This is the record of what happened on a particular job. Which service was quoted? Which edition was used? What did the customer accept? What was delivered? Updating my service information later should not silently change an agreement someone already accepted.

How the system works: a single source of truth for quotes and jobs

Because I was building Client Manager alongside Proposal Builder, I connected them through a shared catalog rather than making each application maintain its own commercial sources.

The shared catalog is a file called catalog.manifest.json. JSON is a plain-text format for structured data. The catalog identifies service IDs, approved editions, source references and hashes. It points to approved Services sources; it does not maintain a second price list. Pricing stays in those approved sources, and any custom job amount is recorded separately on the quote.

A hash is a fingerprint of a file's contents that helps identify the exact version. I use SHA256. If even one character in a file changes, the hash changes. Matching hashes are a reliable way to verify that two files have the same contents. (Microsoft's Get-FileHash documentation covers this, and SHA256 is its default.)

Each quote revision captures its source and pricing snapshot when created. Acceptance locks the specific accepted revision and its supporting evidence; it does not replace the original snapshot. If the source changes later, I can identify that difference and decide what needs attention. If an approved source changes after a quote snapshot, the system can flag it as "Services source changed - review required". I review the difference and decide whether it applies. Reviewing the source, creating a new revision and generating its document are separate steps. A new source edition does not rewrite an accepted agreement. A newer service edition should not quietly rewrite it.

I also started standardizing how I ask AI to work on the system, so new work is checked before it becomes current. The order is always the same: audit, review, approve, generate, verify, promote.

I walk through the catalog, the hashes, and the job snapshot in more detail in the four layers that keep prices and quotes from drifting.

Where does that leave Ross Core IT now?

I verified the connected Services, Proposal Builder and Client Manager workflow end to end in an isolated test. That run covered a source change, review, a new quote revision, real PDF generation, acceptance locking, a blocked edit and a linked amendment. I am extending that tested foundation into Ross Core IT’s operating workflow; the test does not mean every service or ordinary client job is connected yet.

Eventually, I needed to step back and give everything a structure. That's what I mean by building the business behind Ross Core IT.

The website shows what I offer. Behind it, I'm building a consistent way to define that work, quote it, deliver it, and keep a record of what was agreed. I work with people and businesses in Holbrook, Ronkonkoma, Bohemia and across Suffolk County.

Frequently asked questions

What are the four layers?

Owner Development and Strategy, the Commercial Master, Generators and Software Applications, and Client and Job Records. One holds my rules, one holds the approved service information, one uses that information, and one records what was quoted and accepted.

What is catalog.manifest.json?

It identifies service IDs, approved editions, source references and hashes. Applications use it to find approved Services information. The manifest itself is price-free.

What is a hash, in plain terms?

A fingerprint of a file's contents. If even one character changes, the fingerprint changes, so I can tell one version from another.

Does updating a service change a quote someone already accepted?

No. Each quote revision captures its source and pricing snapshot when created. Acceptance locks the specific accepted revision and its supporting evidence; it does not replace the original snapshot.

What's the next step?

Call (631) 229-4446 or use the contact page at rosscoreit.com/contact. By appointment.

Sources

Most of this post is my own experience building my own business. For the technical terms I mention:

  • Microsoft, Get-FileHash (Microsoft.PowerShell.Utility)
  • NIST, FIPS 180-4, Secure Hash Standard (SHS)
  • IETF, RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
  • OpenAI, Codex | AI Coding Partner from OpenAI

Based in Holbrook, NY, serving Holbrook, Ronkonkoma, Bohemia and Suffolk County. Nassau County, Queens and Brooklyn by arrangement, confirmed per job. Suitable services are also available remotely.