There is a huge difference between a project-based bookkeeper and a part-time or full-time bookkeeper.
If you're planning to take on project-based work, or you're about to apply for a part-time or full-time role, read this through to the end. The gap between these two setups is wider than most people think, and walking into one with the mindset of the other is one of the fastest ways to lose a client you could have closed.
I'm Kyle Nelson Omac. I've been a VA bookkeeper for almost five years, and I also run a business focused on fixing the systems and software of companies. I've worked on both sides of this line, so let me walk you through it slowly.
Part-Time and Full-Time Are the Same Category
First, a reframe. Part-time and full-time are not two different categories. They're the same category, which I call the fixed setup. Project-based work is a completely different category of VA bookkeeping.
My first client: a typical fixed setup
My very first personal client was part-time. They already had QuickBooks. Their bank accounts were already connected. My work, day to day, was categorizing transactions and doing bank reconciliations, and everything was already tied into their operations.
It was typical bookkeeping. The system existed. I just had to run it.
My second client: the first project-based one
My second client was also part-time, but this is where my project-based bookkeeping began.
It wasn't a US-based or foreign company. It was a local business: a gadget shop selling cell phones, accessories, and parts. They also handled repairs, so their inventory was full of parts like LCDs, batteries, and charging ports.
That was my first project-based client, and it taught me that this is a completely different kind of job. I'll tell you exactly what happened there in a moment. First, let me define both setups.
What Is a Fixed Setup?
A fixed setup is a VA arrangement where the company already has a system in place.
The structure is already built.
They already have accounting software.
They already have a process.
And you, as the bookkeeper, fill the role they're missing.
That's what makes it fixed, regardless of whether it's full-time, part-time, or flexible. If those criteria are present, it's a fixed setup. You're working like an employee, fulfilling the role of a bookkeeper for that company:
Categorizing transactions daily
Matching receipts
Managing accounts receivable and accounts payable
Running the accounting cycle in the books
Making adjusting entries
Doing bank and credit card reconciliations, and so on
The system exists. The process exists. They're just short on manpower, so they need your help.
What Is a Project-Based Setup?
Project-based is the opposite. Here, there's often nothing in place.
The one keyword to remember is problem. There's a problem that needs a systematic solution.
That could mean the client has no process at all. Maybe they don't have accounting software yet. Their documentation is scattered. They're still running everything on Google Sheets, nothing is centralized, nothing is updated, and the same goes for whatever bank accounts and credit cards the company uses.
Something needs to be organized systematically, process-based or system-based, and the scope is much bigger. You're not filling a seat. You're essentially building their back office.
The Biggest Difference: How You Close the Client
Here's what really matters. The difference isn't only in the work. It's in how you close the client. The approach is completely different.
Closing a fixed-setup client: think like an employee
When a company is looking for a fixed setup, they're looking for someone to fulfill a role.
It doesn't matter if the contract says "independent contractor." It doesn't matter if you invoice them by the hour for what you rendered that week. On paper, you're an independent contractor. You're in the Philippines, they're in another country, so you can't be their employee legally.
But in common sense terms, you're an employee fulfilling the job description they want you to perform. They already know how the process works. They just lack people.
So when you apply for this kind of role, your mind should be in employee mode. And there is nothing wrong with that. Actually, it's exactly right.
You're looking for an opportunity, full-time or part-time. You're willing to work US hours. You're willing to work with a team. You're willing to fulfill your role. That's perfect.
So everything about how you present yourself should match:
Your resume should be employee-type: ATS-friendly, CV-style, and professional-looking.
When they say "Tell me about yourself," you showcase your capabilities, your employment history, your accomplishments in past companies, your skills, and your trainings. You're an applicant looking for an opportunity, and you present yourself like one.
Your attitude shows you're willing to work overtime if needed, willing to work weekends if demand calls for it, and willing to contribute to the company.
That's the perfect way to close a client who wants an employee type.
In my experience, this applies especially to VA agencies. You know the VA agencies here in the Philippines. Whether it's a BPO, an onsite VA agency, or a work-from-home VA agency, they're all employee type. The way you communicate, the way you present yourself, all of it should be employee type. That's the fixed arrangement.
Closing a project-based client: you're the one asking the questions
With a project-based client, it flips completely. You can't bring your employee mindset here.
Why? Because you're not the one being interviewed. You're the one interviewing.
You're the one who needs to ask questions so you can uncover the real problem and figure out what actually needs solving. It's about how you question, how you diagnose, and how you troubleshoot what the company currently needs systematically.
In a fixed setup, you're the one being asked. In a project-based setup, you're the one actively asking:
"Sir, what's the problem in your company right now?"
"What's slowing down your system?"
"What do you want to know? What do you want to see?"
"What do you want to preserve?"
"Which process do you want to speed up?"
"What kind of automation could we apply here?"
"What standard do you want in place so this problem gets solved?"
The way you ask questions determines what problem you uncover, and that determines whether you can provide an accurate solution.
In a fixed setup, you already know what to do, and your employer already knows what you'll do. You just perform the job description they gave you. In a project-based setup, you actively ask so you can deliver the right solution. Before anything else, you need to find the problem.
The Gadget Shop: What a Project-Based Problem Actually Looks Like
Let me go back to my first project-based client, the gadget shop.
Their problem was inventory. They couldn't track it properly. It wasn't real-time. Even when they did periodic inventory counts, there was always an error. There was always a discrepancy. And they had multiple branches.
Then it got worse.
The shop was inside a compound filled with technicians and other gadget shops. Inside that compound, technicians could take parts from the shop and only pay for them once their own customer paid them. The part would leave the shelf, go into a repair, and the shop would only get paid after the technician got paid.
That meant the shop was actually running receivables. Items weren't being paid in cash in real time, so every one of those receivables had to be tracked: who still owes, who has already paid.
And that's where the disputes came in.
A technician would say, "We already paid for that." But there was no proof of payment.
The shopkeeper or store manager would say, "No, that hasn't been paid." So they'd have to go back and review, and that review took time. Hours spent retracing the story just to figure out whether something had really been paid or not.
That's where the problem became clear. Something was slowing them down. There were discrepancies. And they honestly couldn't tell whether theft was happening, because everything was baseless. There was no standard procedure in place, and the documentation was incomplete.
Once I understood that, we fixed the flow and installed accounting software. For this client, we used QuickBooks Online, because I felt it was the right fit for that business: it handles payables, receivables, and inventory, which were exactly the three things they were struggling with.
That was our first project-based client on QuickBooks Online. And notice: none of that would have come out if I had walked in saying, "I'm willing to work overtime, boss."
Why Reading the Client Matters So Much
This is why it's so important to understand who you're talking to. You need to gauge what kind of client is in front of you:
Is this client looking for an employee type?
Or is this client looking for a project-based solution?
It depends on what they're looking for and what their specifications are. Your approach has to match, so you can actually win them over.
Mixing them up is risky.
Bringing a project-based pitch to a fixed-setup client
In an employee-type role, the rate is already set (though it can be negotiable if you want to open that up). More importantly, the job description, the system, and the company's procedures are already given.
If you come in wanting to change their system, that's a red flag for the company. They hired someone to fulfill the role and to help improve things over time, not to overhaul the system just because you were hired. That's a wrong principle, and it's risky. That's probably why you won't get accepted.
Bringing an employee pitch to a project-based client
The reverse fails too. If your lead is project-based and you show up in employee mode: "Sir, I'm willing to work overtime. I can handle it. I can monitor. I can do whatever you ask me to do."
But that's not what they need. They don't need something done. They need something fixed.
There's a difference between ipapagawa (a task to be done) and ipapaayos (something to be fixed). With a task to be done, you already know what to do. With something to be fixed, the client knows there's a problem, but they don't know how to solve it.
So as a VA bookkeeper, you need to know which of the two hats to wear: fixed-based or project-based.
Why I'm Telling You This
Because we, as VA bookkeepers, need to be flexible. And a lot of people don't realize how flexible we need to be.
What works against us is believing coaches who say, flat out, that being a VA bookkeeper is a business, that being a VA is a business, period.
Not always. It really isn't true in every case.
I've just shown you the difference between fixed-based and project-based. If you assume you're always a consultant, always the one solving the problem and contributing to the company systematically, you'll run into trouble, especially with VA agencies. In a VA agency, you need to be employee type. You need to be employee material: someone who works 40 or 20 hours a week and performs the job description you're given. Not someone who's going to bring a brand-new ecosystem into a company that already has one.
As VA bookkeepers, and as virtual assistants in general, we need to think for ourselves. We need to think independently and figure out the right approach for every situation.
Telling everyone to think like a business owner and apply it to every VA bookkeeping situation is the wrong principle. It's misleading advice, because the VA bookkeeping space is so wide. It's not only about being a business owner or being self-employed. It's about how you pace yourself in a dynamic environment, and the VA workspace is very dynamic. We have to adapt to whatever the client actually needs: whether they need an employee, or whether they need someone to provide a solution.
There's no right or wrong here. But at least now, you're aware.
Key Takeaways
Part-time and full-time are the same category (fixed setup). Project-based is a different category entirely.
Fixed setup: the system, software, and process already exist. You fill the role. Present yourself as an employee: ATS-friendly resume, employment history, willingness to work the hours.
Project-based setup: there's a problem and no system to solve it. You're the one interviewing the client. Ask, diagnose, troubleshoot, then build the solution.
Read the client before you pitch. Pitching change to a fixed-setup client is a red flag. Pitching obedience to a project-based client misses the point.
"Being a VA is a business" isn't universal. Adapt to what the client actually needs.
To know more about my services and writings, connect with me here: https://www.kylenelsonomac.com/
Faith without action is Fiction.