Before You Pay: Ask This One Question to Make Accountability Easier

Signing the contract feels like progress.

Paying the invoice feels like commitment.

And in a way, both of those things are progress. They mean a decision has been made. They mean the project is moving out of the “we should do this someday” category and into the “we are actually doing this” category.

But neither one guarantees the outcome you were promised.

That is the part I see people miss all the time.

A contract can define what someone agreed to do. An invoice can show that money changed hands. A proposal can sound compelling. A sales call can feel reassuring. But none of those things, by themselves, tell you whether the work is actually moving toward the result you wanted.

And that gap—the gap between “we hired someone” and “we got the result we paid for”—is where a lot of frustration happens.

I’ve seen this with marketing companies, consultants, developers, coaches, agencies, freelancers, and all kinds of service providers. Someone makes a compelling promise. Maybe they promise more leads. Maybe they promise a better website. Maybe they promise business growth, better systems, improved visibility, more booked calls, a polished brand, better operations, higher conversions, or a strategy that will finally make everything click.

The promise sounds good. The examples look good. The sales process builds confidence.

So you sign.

You pay.

Then 30 days go by.

Then 60.

Then maybe 90.

And when you ask how things are going, you get answers that sound reasonable on the surface but do not actually tell you much.

“We’re making progress.”

“We’re building momentum.”

“These things take time.”

“We’re still in the early stages.”

“We’re laying the foundation.”

“We’re optimizing.”

“We’re working through the process.”

Maybe all of that is true.

Some things really do take time. Not every result is instant. Marketing takes time. SEO takes time. Building a quality website takes time. Consulting takes time if meaningful change is involved. A good strategy often needs room to develop, test, adjust, and improve.

But here is the key question:

What exactly are we measuring?

Because if nobody defined that before the work started, you may not have a real way to know whether things are going well or not.

You just have a feeling.

And feelings are not a great way to manage accountability.

That is where check-ins and KPIs matter.

Before the work starts, decide what success is supposed to look like. Not just the big dream outcome at the end, but the milestones along the way. What should be reviewed? What should be completed? What should be measured? What should be improving? What decisions need to be made? What signs would indicate that the work is on track?

This is one of the simplest ways to protect yourself when you hire someone for an important outcome.

It is also one of the simplest ways to create a better working relationship with the person or company you hire.

Because accountability is not supposed to be a punishment. It is supposed to be part of the plan.

The promise is not the same as the process

One of the reasons people get into trouble is that they focus too much on the promise and not enough on the process.

The promise is usually the exciting part.

More leads.

More sales.

A new website.

A better brand.

A stronger online presence.

A scalable system.

A clearer strategy.

A smoother operation.

A higher return on ad spend.

A more professional business.

That is the part people want. And that is understandable. Nobody hires a marketing company because they want reports. Nobody hires a web developer because they love project management. Nobody hires a consultant because they want more meetings on their calendar.

You hire someone because you want an outcome.

But the outcome is not magic. There is a path between where you are now and where you want to be. That path usually includes decisions, deliverables, reviews, approvals, deadlines, metrics, changes, and tradeoffs.

If the path is not clear, you can end up with a very strange situation:

You paid for a result, but all you can see is activity.

And activity can be deceiving.

Hours worked can look impressive.

Emails sent can look impressive.

Meetings held can look impressive.

Tasks completed can look impressive.

Reports generated can look impressive.

But activity and results are not automatically the same thing.

A vendor can be very busy and still not be moving you toward the business outcome you hired them for. A team can send a lot of emails and still not be solving the real problem. A consultant can hold a lot of calls and still not help you make the decisions that matter. A marketing agency can show a lot of campaign activity and still not generate qualified leads. A developer can write a lot of code and still not deliver the site or feature you actually need.

That does not always mean bad intentions. Sometimes it is just poor structure. Sometimes expectations were never made specific. Sometimes both sides assumed they were talking about the same thing when they were not.

That is why the process matters.

The promise gets you excited.

The process tells you whether the promise is becoming real.

Define success before the work starts

Before work begins, one of the most important things you can do is define what success is supposed to look like.

And I do not mean in vague terms.

“Grow the business” is not specific enough.

“Improve the website” is not specific enough.

“Get better marketing results” is not specific enough.

“Help with strategy” is not specific enough.

“Make things look more professional” is not specific enough.

Those may be useful starting points, but they are not enough to manage a paid engagement.

You need to decide what success means in practical terms.

If this is an advertising campaign, success might include things like:

Qualified leads.

Cost per lead.

Booked appointments.

Sales.

Conversion rate.

Click-through rate.

Return on ad spend.

Lead quality.

Follow-up rate.

Landing page performance.

Time from lead to booked call.

If this is a website project, success might include:

Agreed milestones.

Launch dates.

Completed features.

Approved designs.

Finished content.

Testing.

Mobile responsiveness.

Page speed.

Functional forms.

Tracking setup.

SEO basics.

E-commerce checkout testing.

Bug fixes.

Training or handoff.

If this is consulting, success might include:

Specific actions completed by certain dates.

Decisions made.

Systems documented.

Team responsibilities clarified.

Processes improved.

Problems identified.

Recommendations delivered.

Implementation steps completed.

Review meetings held.

Accountability for follow-through.

If this is branding, success might include:

Research completed.

Messaging approved.

Logo concepts delivered.

Design direction agreed upon.

Brand guidelines completed.

Final assets delivered.

Usage files provided.

Website or marketing materials updated.

If this is SEO, success might include:

Technical audit completed.

Keyword research delivered.

Content plan approved.

Pages optimized.

New content published.

Indexing issues fixed.

Local listings improved.

Rankings monitored.

Organic traffic reviewed.

Conversions from organic traffic tracked.

The exact KPIs and milestones depend on the type of work. The point is not that every project should use the same metrics. The point is that the metrics should match the outcome.

If you are paying for leads, you should not only be reviewing impressions.

If you are paying for sales, you should not only be reviewing clicks.

If you are paying for a finished website, you should not only be reviewing “hours worked.”

If you are paying for consulting, you should not only be reviewing how many meetings happened.

If you are paying for strategy, you should not only be reviewing how polished the slide deck looks.

You need to know what actually indicates progress toward the result you wanted.

A KPI is not just a number someone reports

A KPI—key performance indicator—gets talked about a lot, but not always clearly.

A KPI is not just a number on a report.

A KPI should tell you whether the work is actually moving toward the business outcome you hired someone for.

That distinction matters.

Because it is very easy to report numbers that look official but do not really answer the important question.

For example, if you hire someone to generate leads, they might report:

Impressions.

Reach.

Clicks.

Website visits.

Ad spend.

Engagement.

Those numbers may be useful. They might help diagnose what is happening. But they do not automatically prove the campaign is working.

If the real goal is qualified leads, then you need to review qualified leads. If the real goal is booked appointments, then you need to review booked appointments. If the real goal is sales, then you need to review sales or at least the steps that lead directly to sales.

A campaign with lots of impressions but no qualified leads may not be working.

A campaign with lots of clicks but no conversions may not be working.

A campaign with cheap leads that never answer the phone may not be working.

A campaign with a great cost per click but poor lead quality may not be working.

The same thing applies to website projects.

If you hire someone to build a website, “we worked 40 hours this month” may be true. But what was completed? What was approved? What is still missing? What blockers exist? Are the major pages done? Are the forms working? Has the content been entered? Has the responsive design been checked? Has the site been tested? Is the launch date still realistic?

Hours matter in some billing arrangements, but hours alone do not tell you whether the project is on track.

For consulting, a report that says “we had four meetings this month” may be accurate. But what changed as a result of those meetings? What decisions were made? What actions were assigned? What deadlines were attached? What was implemented? What needs to happen before the next review?

Again, activity is not the same as progress.

A useful KPI should make the work more visible and more accountable.

It should help both sides answer:

Are we moving in the right direction?

Are we on schedule?

Are we getting closer to the outcome?

What needs to change?

What is working?

What is not working?

What decision needs to be made next?

If the KPI does not help answer those questions, it may not be the right KPI.

Schedule the check-ins before there is a problem

Another major mistake is waiting until you are frustrated to ask for accountability.

By then, the conversation is harder.

If 60 or 90 days have gone by and you suddenly say, “I want weekly updates and detailed reporting,” that may be reasonable, but now it is happening in a tense context. The vendor may feel like they are being attacked. You may feel like you are being ignored. Everyone is reacting to frustration instead of following a process.

That is why check-ins should be scheduled before there is a problem.

Weekly, biweekly, monthly—whatever makes sense for the type of work.

Not every project needs weekly meetings. Some do. Some would be better with a short written update every week and a deeper meeting once a month. Some fast-moving projects need frequent contact. Some longer-term strategy or SEO projects may need monthly reporting and quarterly reviews.

The format matters less than the agreement.

What matters is that both sides know:

When will we review progress?

What will we review?

Who needs to be there?

What numbers or milestones will be discussed?

What decisions might need to be made?

What happens if something is off track?

What does the vendor need from me?

What do I need from the vendor?

Check-ins make the work visible.

They also create a rhythm. Instead of wondering what is happening behind the scenes, you have a scheduled moment to look at the project together. Instead of assuming everything is fine until the deadline is missed, you have a chance to catch problems early.

That can save a lot of pain.

A missed milestone detected early is manageable.

A missed milestone discovered at the very end is a crisis.

A campaign that is underperforming after two weeks can be adjusted.

A campaign that burns through three months of budget with no meaningful review is a problem.

A website project that is waiting on content can be discussed.

A website project that silently stalls because nobody clarified content responsibilities can become a mess.

A consulting engagement where nobody completes assigned actions can be redirected.

A consulting engagement where everyone just keeps meeting without implementation can become expensive theater.

Accountability works much better when it is part of the agreement from the beginning.

Accountability protects both sides

It is easy to think of accountability as something that protects the client from the vendor.

And it does.

If you are paying someone, you should know what you are paying for. You should be able to see whether the work is happening. You should have an agreed way to measure progress. You should not have to wait until the very end to find out whether anything useful was accomplished.

But accountability also protects the vendor.

A good vendor should want clear expectations.

A good vendor should want to know what success means.

A good vendor should want regular check-ins because those check-ins create opportunities to get feedback, remove blockers, and prevent misunderstandings.

If the client is supposed to provide content, approvals, access, feedback, or decisions, regular check-ins make that visible too.

Sometimes projects stall because the vendor is not doing what they promised.

But sometimes projects stall because the client has not provided what the vendor needs.

Maybe the client needs to approve a design.

Maybe the client needs to provide logins.

Maybe the client needs to review copy.

Maybe the client needs to make a decision about budget.

Maybe the client needs to train their sales team to follow up with the leads.

Maybe the client needs to clarify who has authority to approve the work.

Good accountability exposes all of that.

It keeps both sides honest.

It turns vague frustration into specific discussion.

Instead of “this is taking forever,” the conversation becomes, “The design was due last Friday, the content is still missing, and the launch date depends on both being completed by next Wednesday.”

Instead of “the marketing is not working,” the conversation becomes, “We generated 42 leads, 18 were qualified, 9 booked calls, and 3 became proposals. The issue appears to be in the follow-up process or the offer, not just the ads.”

Instead of “the consulting is not helping,” the conversation becomes, “We identified the bottleneck, assigned three process changes, but only one has been implemented. Let’s decide whether the issue is capacity, ownership, or priority.”

Specific accountability makes better conversations possible.

Beware of vague progress language

There are certain phrases that should make you slow down and ask for clarification.

“We’re making progress.”

“We’re building momentum.”

“We’re optimizing.”

“We’re working on it.”

“We’re in the strategy phase.”

“We’re testing.”

“We’re still gathering data.”

“We’re refining the approach.”

None of those phrases are automatically bad. They can all be legitimate.

There really is such a thing as optimization.

There really is such a thing as testing.

There really is such a thing as strategy.

There really is such a thing as early-stage momentum.

But vague language should lead to specific follow-up questions.

What progress exactly?

What momentum are we seeing?

What are we optimizing?

What did the test show?

What data have we gathered?

What did we learn?

What changed because of that learning?

What is the next milestone?

What should be different by the next check-in?

What are we measuring?

A provider who knows what they are doing should be able to answer those questions in a way that makes sense.

They may not always have perfect news. That is fine. Not every check-in has to be full of wins. Sometimes the honest answer is, “This is not performing the way we expected, here is what we think is happening, and here is what we recommend changing.”

That is still a useful answer.

In fact, that kind of answer can build trust.

What damages trust is when every update sounds positive but nothing concrete is being shown.

If all you are getting is reassurance, not evidence, you may have a problem.

The scoreboard matters

One of the simplest ways to think about this is the idea of a scoreboard.

If you are buying an important outcome, you need some kind of scoreboard.

Not because every project is a game.

Not because every relationship should be adversarial.

But because without a scoreboard, nobody really knows the score.

If you hire someone for an outcome and there is no agreed way to review progress, you are depending on their interpretation of how things are going. And their interpretation may be different from yours.

They may think the campaign is succeeding because traffic is up.

You may think it is failing because sales are flat.

They may think the website project is going fine because development is underway.

You may think it is failing because the launch date is slipping.

They may think consulting is successful because the meetings are productive.

You may think it is failing because nothing is being implemented.

Both sides might be sincere. But if there is no scoreboard, the disagreement becomes subjective.

That is dangerous.

A scoreboard does not have to be complicated. In many cases, it can be very simple.

For a website project, it might be a milestone chart:

Discovery complete.

Sitemap approved.

Design approved.

Content delivered.

Development complete.

Testing complete.

Launch complete.

Training complete.

For an ad campaign, it might be a monthly performance review:

Spend.

Leads.

Qualified leads.

Cost per qualified lead.

Booked calls.

Sales.

Conversion rate.

Notes and next actions.

For consulting, it might be an action tracker:

Issue identified.

Recommendation made.

Owner assigned.

Deadline set.

Status reviewed.

Result measured.

Next decision required.

The scoreboard should match the work.

But there should be a scoreboard.

Because if nobody can answer what will be reviewed along the way, you may be buying a promise with no way to measure whether it is becoming reality.

Ask the right question before handing over the money

Before paying someone for an important outcome, ask this question:

“What will we review together along the way that proves this is working?”

That question is simple, but it reveals a lot.

It forces the conversation out of the abstract and into the practical.

If someone says they are going to improve your marketing, what will you review together that proves the marketing is improving?

If someone says they are going to build your website, what will you review together that proves the project is on track?

If someone says they are going to help you grow your business, what will you review together that proves the work is creating meaningful progress?

If someone says they are going to help with operations, what will you review together that proves the operation is getting better?

The answer does not have to be perfect or overly complex. But there should be an answer.

A strong answer might sound like:

“We’ll review lead volume, lead quality, cost per lead, booked appointments, and conversion to sales every month. In the first 30 days, we’ll focus on setup and baseline data. By day 60, we should have enough early performance data to start making adjustments.”

Or:

“We’ll use a project timeline with milestones. Every week, we’ll review what was completed, what is waiting on approval, what is blocked, and whether the launch date is still on track.”

Or:

“We’ll create a list of action items after each consulting session. At each review, we’ll look at what was completed, what decisions were made, what is still unresolved, and what business metric or operational issue the work is meant to improve.”

A weak answer might sound like:

“Don’t worry, we’ll keep you updated.”

Or:

“It’s too early to think about that.”

Or:

“These things are hard to measure.”

Or:

“Just trust the process.”

Or:

“We don’t really do reporting.”

Again, not everything can be measured the same way. Some work is more qualitative than quantitative. A branding project is not always measured like an ad campaign. A leadership consulting engagement is not always measured like an e-commerce funnel.

But even qualitative work can have milestones, deliverables, decisions, and review points.

If someone cannot explain what you will review together along the way, that is a warning sign.

You may be buying a promise with no scoreboard.

And that is dangerous.

Contracts matter, but they are not enough

I am not saying contracts do not matter.

They absolutely matter.

A contract can define scope, payment terms, timelines, responsibilities, ownership, cancellation terms, deliverables, and legal protections. You should care about those things.

But a contract is not the same as active accountability.

A contract usually tells you what was agreed to.

Check-ins tell you what is happening now.

KPIs tell you whether the work is producing the result.

You need all three.

A contract without check-ins can leave you in the dark.

Check-ins without KPIs can become vague conversations.

KPIs without a clear contract can create confusion about responsibilities.

The best situation is when all three work together.

The contract defines the agreement.

The check-ins keep the work visible.

The KPIs clarify whether the work is moving toward the outcome.

That combination gives you a much better chance of catching problems early, making informed decisions, and avoiding the kind of unpleasant surprise where you reach the end of the engagement and realize you did not get what you thought you were paying for.

Do not wait until the end to find out if it worked

One of the worst ways to manage a project or campaign is to wait until the end and then ask, “Did it work?”

By then, your options may be limited.

The budget may be spent.

The deadline may be gone.

The launch may be delayed.

The campaign may have burned through valuable time.

The opportunity may have passed.

The relationship may already be strained.

It is much better to ask along the way:

Is this working?

How do we know?

What are we seeing?

What are we not seeing?

What needs to change?

What is the next checkpoint?

What decision needs to be made?

What result should we expect by the next review?

This does not mean you should panic if results are not instant. That is not the point.

The point is to create visibility.

Some work needs time, but time should not be used as a substitute for accountability.

If something takes six months, then there should be meaningful things to review during those six months.

If a campaign needs 90 days to optimize, then there should still be early indicators.

If a website takes three months to build, there should still be milestones.

If consulting requires ongoing work, there should still be actions and decisions between calls.

Waiting until the end is risky because it turns accountability into a postmortem.

By then, you are not managing the work. You are just evaluating the damage.

A better way to hire

The next time you are about to hire someone for an important outcome, slow down before you sign and pay.

Do not only ask:

How much does it cost?

When can you start?

What is included?

Have you done this before?

Those are useful questions, but they are not enough.

Also ask:

What will we review together along the way?

What milestones should we expect?

What KPIs make sense for this work?

How often will we check in?

What will the reporting look like?

What does success look like at 30 days, 60 days, and 90 days?

What do you need from me to keep this on track?

What happens if the numbers are not where we want them to be?

What happens if a deadline is missed?

How will we know whether this is working?

Those questions do not make you difficult. They make you responsible.

A serious professional should not be offended by them. They may even appreciate them, because clear expectations make the engagement healthier for everyone.

The wrong provider may resist those questions because vague promises are easier to sell than measurable progress.

That is exactly why you should ask.

Make the invisible visible

A lot of service work is invisible while it is happening.

Marketing strategy can be invisible.

Website development can be invisible.

Consulting can be invisible.

SEO can be invisible.

Planning, analysis, testing, troubleshooting, research, and optimization can all happen behind the scenes.

That does not mean the work is not real.

But invisible work still needs visible accountability.

You do not need to micromanage every task. You do not need to demand constant updates. You do not need to turn every relationship into a courtroom cross-examination.

But you do need enough visibility to know whether the work is moving forward.

There is a big difference between trusting someone and having no idea what is happening.

Trust and accountability are not opposites.

In a healthy business relationship, they support each other.

The more clear the accountability, the easier it is to trust the process.

The more vague the process, the harder it becomes to trust even good intentions.

The bottom line

Signing the contract feels like progress.

Paying the invoice feels like commitment.

But the real question is what happens after that.

What gets reviewed?

What gets measured?

What gets completed?

What gets adjusted?

What gets decided?

What proves that the work is moving toward the outcome you hired someone for?

Before you hand over money for an important result, ask:

“What will we review together along the way that proves this is working?”

If the answer is clear, you are in a much better position to manage the relationship, understand progress, and hold everyone accountable.

If nobody can answer that clearly, be careful.

You may be buying a promise with no scoreboard.

And once the money changes hands, you should not have to wait until the very end to find out whether you got what you paid for.