Already in your Microsoft licence.

Used for three things by one person.

If your agency runs on Microsoft 365, Power Automate is probably already paid for, and it is a reasonable fit for the work that happens around documents and approvals rather than inside the ATS.

Stack Logic builds the flows properly, including the exception handling most in-house builds are missing.

Already in your Microsoft licence.

Used for three things by one person.

If your agency runs on Microsoft 365, Power Automate is probably already paid for, and it is a reasonable fit for the work that happens around documents and approvals rather than inside the ATS.

Stack Logic builds the flows properly, including the exception handling most in-house builds are missing.

Exception handling

The tidy cases should never reach a person.

Contract generation, placement paperwork, compliance document collection, timesheet exceptions and anything that needs a manager to say yes before it moves. That is Power Automate's home ground.

The part most in-house builds are missing is what happens when a case does not reconcile. A flow that only handles the tidy cases hands everything else back with no explanation, and someone ends up checking all of it again to find out which ones failed.

Built properly, the straightforward cases pass through untouched and only the exceptions reach a person, arriving already diagnosed with the specific mismatch named.

Exception handling

The tidy cases should never reach a person.

Contract generation, placement paperwork, compliance document collection, timesheet exceptions and anything that needs a manager to say yes before it moves. That is Power Automate's home ground.

The part most in-house builds are missing is what happens when a case does not reconcile. A flow that only handles the tidy cases hands everything else back with no explanation, and someone ends up checking all of it again to find out which ones failed.

Built properly, the straightforward cases pass through untouched and only the exceptions reach a person, arriving already diagnosed with the specific mismatch named.

What I build

What a Power Automate build actually looks like.

The work sits where Microsoft 365 already lives: documents, approvals, SharePoint and the inbox. Where the ATS is involved, the flow talks to it through its API rather than through a person retyping.

Placement and extension processes

End to end, from the point a consultant submits something, through the approval chain, to the signed document landing where finance expects it. Nobody chases a signature and nobody wonders which version is current.

Bullhorn and SharePoint integration

A document filed against the right record without anyone dragging a file into a folder. The ATS and the document library agree about where things live, which is rarer than it sounds.

Document data extraction

Using AI where the input is a PDF that arrives in a slightly different shape each time, with a review step before anything commits. A person sees what was read before it becomes permanent.

Exception handling

The straightforward cases pass through and only the ones that do not reconcile reach a person, named and diagnosed. This is the part most in-house builds skip, and the part that makes the rest trustworthy.

What I build

What a Power Automate build actually looks like.

The work sits where Microsoft 365 already lives: documents, approvals, SharePoint and the inbox. Where the ATS is involved, the flow talks to it through its API rather than through a person retyping.

Placement and extension processes

End to end, from the point a consultant submits something, through the approval chain, to the signed document landing where finance expects it. Nobody chases a signature and nobody wonders which version is current.

Bullhorn and SharePoint integration

A document filed against the right record without anyone dragging a file into a folder. The ATS and the document library agree about where things live, which is rarer than it sounds.

Document data extraction

Using AI where the input is a PDF that arrives in a slightly different shape each time, with a review step before anything commits. A person sees what was read before it becomes permanent.

Exception handling

The straightforward cases pass through and only the ones that do not reconcile reach a person, named and diagnosed. This is the part most in-house builds skip, and the part that makes the rest trustworthy.

Is this you?

We should talk if...

Your agency runs on Microsoft 365, and some version of the following is true.

One person built three flows two years ago and nobody else dares touch them.

Placement paperwork still moves by email attachment, and the current version of a contract is whichever one was sent last.

Timesheets that do not reconcile get found at invoicing rather than at submission.

None of this needs new software. Most of it needs the licence you already pay for, used properly, with the messy tenth of cases routed to a person instead of buried.

Is this you?

We should talk if...

Your agency runs on Microsoft 365, and some version of the following is true.

One person built three flows two years ago and nobody else dares touch them.

Placement paperwork still moves by email attachment, and the current version of a contract is whichever one was sent last.

Timesheets that do not reconcile get found at invoicing rather than at submission.

None of this needs new software. Most of it needs the licence you already pay for, used properly, with the messy tenth of cases routed to a person instead of buried.

How it works

Every process goes through the same three steps.

Discovery

A focused look at where documents, approvals and exceptions actually move through the business, and which of the current flows are load-bearing. We agree what stays in Power Automate, what needs the API, and whether anything you want depends on premium connectors, before anything is built. This takes a week.

Discovery

A focused look at where documents, approvals and exceptions actually move through the business, and which of the current flows are load-bearing. We agree what stays in Power Automate, what needs the API, and whether anything you want depends on premium connectors, before anything is built. This takes a week.

Build

I build the flows we have agreed, with exception paths designed in from the start rather than bolted on after the first failure. Anything past Power Automate's comfortable complexity moves into code, and everything is documented as it is built. Typically two to four weeks depending on scope.

Build

I build the flows we have agreed, with exception paths designed in from the start rather than bolted on after the first failure. Anything past Power Automate's comfortable complexity moves into code, and everything is documented as it is built. Typically two to four weeks depending on scope.

Handover

You get working flows, documentation of what runs when and where to look when it does not, and error alerting so a failure reaches a person rather than a log. I stay available for 30 days post-launch, with retainer support after that if you want it.

Handover

You get working flows, documentation of what runs when and where to look when it does not, and error alerting so a failure reaches a person rather than a log. I stay available for 30 days post-launch, with retainer support after that if you want it.

what clients say

But don't just take it from me.

We bring Jack in whenever we need serious Bullhorn Automation expertise. He takes our most tangled requirements and turns them into clean automations that just work, and he's become our go-to second pair of eyes whenever a build needs sense-checking. It's clear he has a deep understanding of Bullhorn and the recruitment industry as a whole. Overall, he's saved us hours of build time.

Kathy Walker, Fractional Marketing Director & Co-Founder, JK&Co.

We’ve had the pleasure of working with Jack across several projects and have consistently been impressed with the quality of work delivered. Communication is always clear, deadlines are met without issue, and there's a strong sense of accountability and transparency throughout. What stands out most is the flexibility to adapt to varying requirements while maintaining a high standard of execution.

Tina Tucker, Marketing Account Director, Thrive Recruitment Marketing

what clients say

But don't just take it from me.

We bring Jack in whenever we need serious Bullhorn Automation expertise. He takes our most tangled requirements and turns them into clean automations that just work, and he's become our go-to second pair of eyes whenever a build needs sense-checking. It's clear he has a deep understanding of Bullhorn and the recruitment industry as a whole. Overall, he's saved us hours of build time.

Kathy Walker, Fractional Marketing Director & Co-Founder, JK&Co.

We’ve had the pleasure of working with Jack across several projects and have consistently been impressed with the quality of work delivered. Communication is always clear, deadlines are met without issue, and there's a strong sense of accountability and transparency throughout. What stands out most is the flexibility to adapt to varying requirements while maintaining a high standard of execution.

Tina Tucker, Marketing Account Director, Thrive Recruitment Marketing

what clients say

But don't just take it from me.

We bring Jack in whenever we need serious Bullhorn Automation expertise. He takes our most tangled requirements and turns them into clean automations that just work, and he's become our go-to second pair of eyes whenever a build needs sense-checking. It's clear he has a deep understanding of Bullhorn and the recruitment industry as a whole. Overall, he's saved us hours of build time.

Kathy Walker, Fractional Marketing Director & Co-Founder, JK&Co.

We’ve had the pleasure of working with Jack across several projects and have consistently been impressed with the quality of work delivered. Communication is always clear, deadlines are met without issue, and there's a strong sense of accountability and transparency throughout. What stands out most is the flexibility to adapt to varying requirements while maintaining a high standard of execution.

Tina Tucker, Marketing Account Director, Thrive Recruitment Marketing

Book a Call

Book a Diagnostic Call

The diagnostic call is 30 minutes. You tell me what runs on Microsoft 365 and where the paperwork sticks, and I'll tell you honestly what belongs in Power Automate, what needs code, and whether any of it needs a premium connector before you commit to one. If the flow you need already exists in your tenant half-built, I'll say so.

Trusted by SMEs from Recruitment and HR to Marketing, Finance and Tech.

frequently asked questions

Common questions answered

Do we need extra licences for this?

Sometimes. Plenty of useful flows run on the licences you already have, but some connectors Microsoft classes as premium, which is a per-user cost on top of what you already pay. It depends on which systems the flow touches. I will tell you before we design around one, so the decision is made on price rather than discovered on the invoice.

Do we need extra licences for this?

Sometimes. Plenty of useful flows run on the licences you already have, but some connectors Microsoft classes as premium, which is a per-user cost on top of what you already pay. It depends on which systems the flow touches. I will tell you before we design around one, so the decision is made on price rather than discovered on the invoice.

Can Power Automate talk to Bullhorn?

Yes, through the REST API rather than a ready-made connector doing everything for you. Triggering a flow when a placement is confirmed, filing a document against the right record in SharePoint, and writing status back to Bullhorn are all routine once the connection is built. The part that needs care is matching records reliably, which is the same problem it always is.

Can Power Automate talk to Bullhorn?

Yes, through the REST API rather than a ready-made connector doing everything for you. Triggering a flow when a placement is confirmed, filing a document against the right record in SharePoint, and writing status back to Bullhorn are all routine once the connection is built. The part that needs care is matching records reliably, which is the same problem it always is.

We already have flows someone built in-house. Do you replace them?

Only where it earns its keep. Working flows stay. The usual problems are that nobody documented them, one person understands them, and the failure cases were never designed. Often the fix is documentation, alerting and an exception path added to what exists, which is cheaper than a rebuild and less disruptive.

We already have flows someone built in-house. Do you replace them?

Only where it earns its keep. Working flows stay. The usual problems are that nobody documented them, one person understands them, and the failure cases were never designed. Often the fix is documentation, alerting and an exception path added to what exists, which is cheaper than a rebuild and less disruptive.

When does Power Automate stop being the right tool?

At a certain complexity. Once a flow has more than a couple of dozen steps and several branches, it becomes difficult to debug and expensive to change, and it is usually cheaper to move that logic into code and leave Power Automate handling the Microsoft-facing parts it is good at. I build both, so the recommendation is not tied to a preference.

When does Power Automate stop being the right tool?

At a certain complexity. Once a flow has more than a couple of dozen steps and several branches, it becomes difficult to debug and expensive to change, and it is usually cheaper to move that logic into code and leave Power Automate handling the Microsoft-facing parts it is good at. I build both, so the recommendation is not tied to a preference.

Can it read the PDFs our contractors send?

Usually, and this is where a model earns its place. Timesheets and compliance documents arrive in a slightly different shape each time, which defeats template-based extraction. A model reads them into structured data, a review step shows a person what was read, and only then does anything commit. Nothing writes into a record silently.

What does it cost?

It depends on how many flows are involved and how much of the process needs untangling first. Custom builds start at £3,000, fixed price and phased, so you can stop after a phase if it is not working out. If what you need is genuinely three tidy flows on standard connectors, it will land at the lower end and I will say so. The diagnostic call is free.

What does it cost?

It depends on how many flows are involved and how much of the process needs untangling first. Custom builds start at £3,000, fixed price and phased, so you can stop after a phase if it is not working out. If what you need is genuinely three tidy flows on standard connectors, it will land at the lower end and I will say so. The diagnostic call is free.

See where your team's time is going.

It starts with a short audit of your stack. I'll show you where consultant and back-office hours are leaking, and what it would take to get them back.

Systems That Scale.

© 2026 Stack Logic. All rights reserved.
Here's our privacy policy.

See where your team's time is going.

It starts with a short audit of your stack. I'll show you where consultant and back-office hours are leaking, and what it would take to get them back.

Systems That Scale.

© 2026 Stack Logic. All rights reserved.
Here's our privacy policy.