Search creators⌘K
  1. Home
  2. Creators
  3. Bojan Radojicic

Bojan Radojicic

Bojan Radojicic writes about building more efficient finance teams, including FP&A templates, finance automation, and practical uses of AI in reporting.

336K followersAI in financeBased on 9 posts · latest Oct 2026
LinkedIn

At a glance

Bojan Radojicic is most useful for finance automation and FP&A template messaging to finance leaders.

Best for

A finance software company selling FP&A planning and reporting tools, for co-marketing on automation and templates.

Not for

Developer-tools companies targeting platform engineers who influence tooling purchases.

Key takeaways

  • Skilled finance people are being used as data clerks.
  • Templates, not software purchases, separate good finance teams from world-class ones.
  • AI should write the words, not calculate the numbers.

Check first: Confirm LinkedIn audience demographics by role, seniority, geography, and recent post performance.

Main ideas
Skilled finance people are being used as data clerks · Templates, not software purchases, separate good finance teams from world-class ones · AI should write the words, not calculate the numbers
Audience
335,767 LinkedIn followers · 843 Instagram followers
Read first
A finance team builds its own reporting app with Claude Code, Cloudflare and GitHub
Sources for this section

What they are known for

Bojan Radojicic writes about making finance teams more efficient, especially through better FP&A templates and practical automation.

  • The posts show three sides of that work: diagnosing spreadsheet-heavy reporting, explaining how a small finance team could build a custom reporting app, and describing finance leaders’ dissatisfaction with accounts-payable tools.
  • The clearest starting point is the reporting-app post: it lays out what the app would do and the safeguards needed before using real data.
  • They also show a recurring concern: automation should free skilled finance staff from manual work without sacrificing accuracy or review.

Radojicic connects familiar finance-team problems to specific ways of working, rather than treating software as the answer by itself.

  • An FP&A post moves from broken spreadsheets and three-day variance comments to reusable templates, including rolling forecasts and driver-based models.
  • A separate app-building post pairs a practical tool stack with firm controls: code calculates and reconciles figures, people review AI-written commentary, and a developer checks the system before real data is used.
  • The accounts-payable post is a useful counterpoint: it draws on a survey of 102 finance leaders and broadens the question from choosing an AP tool to improving automation across the finance function.
  • Follow them for concrete examples of finance-process problems, reusable FP&A resources, and an emphasis on controls when applying AI.
Sources for this section

Ideas and priorities

Bojan Radojicic argues that finance teams lose their strongest people to manual collection, reconciliation and commentary, and that the fix is better templates, automation and AI under explicit rules.

Read more

Across three LinkedIn posts, the emphasis is on standards and controls rather than software purchases: templates are infrastructure a team owns, code does the calculating, AI writes the words, and a human reviews every comment before it reaches a CFO. The posts make their case through short diagnostic stories and survey numbers, each ending with a named deliverable—a template pack, a build checklist, or an event.

Skilled finance people are being used as data clerks

The problem is not weak talent or effort; it is the work itself.

Read more

Teams spend months collecting, reconciling and formatting numbers, then write commentary late at night under pressure.

  • Management sees the story days after the numbers.
  • The post argues this is a management choice, not a staffing fact: the same analysts who could build a rolling forecast spend their weeks repairing spreadsheets.

An FP&A team Radojicic says they audited worked 70-hour weeks with static spreadsheets, broken VLOOKUPs and manual variance comments that took three days to write. When the CFO asked for a 12-month rolling forecast, the room went silent: no model existed, so the team had to build one from scratch again.

Read original

Templates, not software purchases, separate good finance teams from world-class ones

The post distinguishes tools from standards.

Read more

A team owns the templates it builds and maintains, and those standards determine whether a recurring close is a scramble or a routine update. Without them, teams reinvent the same models every month.

Seven must-have FP&A templates every professional should master, from 3-statement models to driver-based forecasting. The claim: once they are ready, a monthly fire drill becomes a 10-minute update.

Read original

AI should write the words, not calculate the numbers

When AI enters reporting, Bojan Radojicic draws a hard line between computation and language.

Read more

They say code computes every figure and reconciles it to the trial balance; AI only drafts commentary.

  • Line owners review and edit every comment before it reaches the CFO, and a developer reviews the code and infrastructure before real data is used.
  • Speed without control is a risk.
  • Security is mandatory: login with MFA, role-based access, a full audit trail, and review and approval options.

A custom reporting app built with Claude Code, Git/GitHub and Cloudflare pulls trial balances, budgets and forecasts from a Drive folder; produces P&L, balance sheet and cash flow in management format; compares actuals against budget, forecast and last year; and drafts variance commentary with suggested action plans. The post puts a realistic first version at 10 to 14 weeks and says one such app is already being built for one of Radojicic's companies.

The post says a recent change has made guardrails more urgent: in the last year, a finance leader and a small team became able to describe rules in plain English and get working software. Controls now have to be designed alongside the build.

Read original

Automation is a function-wide design question, not a tool purchase

Survey data on accounts payable shows finance teams know what is broken but lack a clear path to fixing it.

Read more

AP is often where the automation gap is felt first, but it is rarely the only place. The post shifts the question from which AP tool to buy to how to build a finance function where automation and AI work end to end, then points to its own event as a place to work that out.

The post reports that, of 102 finance leaders surveyed—mostly CFOs, VPs and finance directors—only 18% were happy with their AP solution; 33% still run AP manually or inside their ERP with no dedicated tool; 50% say their current solution could be better or that they are not satisfied; and 65% want their provider to bring more automation and AI. Approvals and payments and invoice capture tied as the biggest automation opportunity, at 22% each.

Read original

Sources for this section

Start with their work

Bojan Radojicic on YouTube

A finance team builds its own reporting app with Claude Code, Cloudflare and GitHub

Answers the question "can a small finance team realistically build its own reporting automation, and what would make that safe?"

Read more

A newcomer should start here: it is the most concrete build walkthrough in Bojan Radojicic's posts, naming the tools, spelling out the guardrails and giving a realistic timeline instead of a general AI pitch.

Bojan Radojicic describes a CFO asking how to automate reporting work that falls between existing systems.

  • Month-end close in small companies takes six to seven days, five of them spent collecting, reconciling and formatting numbers.
  • The post lists the costs: commentary written late at night under pressure, management seeing the story days after the numbers, and strong analysts used as data clerks.
  • The build idea is specific.
  • A finance leader and a small team describe their rules in plain English; Claude Code writes the code, Git and GitHub track changes, and Cloudflare hosts the app behind a secure login.
  • A basic version pulls trial balances, budgets and forecasts from a Drive folder; builds P&L, balance sheet and cash flow in management format; compares actuals against budget, forecast and last year; and drafts variance commentary with suggested action plans.
  • Three rules keep it trustworthy: code calculates every figure and reconciles it to the trial balance while AI writes only the words; line owners review and edit every comment before it reaches the CFO; and a developer reviews the code and infrastructure before real data goes in.
  • Security requirements include company login with MFA, role-based access, a full audit trail, and review and approval options.
  • The post puts a realistic first version at 10 to 14 weeks and says they are currently building one app for one of their companies.
  • It also points to a newsletter that reaches 90,000 finance readers.

For brands planning a campaign

This is a buyer's mental model: automation is acceptable when it is governed, auditable and keeps a human between the draft and the CFO.

  • A finance software company could co-market around that frame with a joint build walkthrough or a checklist of the three rules and security requirements, rather than a generic AI story.
  • The newsletter is also a concrete distribution channel to explore.

The FP&A fire drill and the seven templates that shorten it

Answers the question "what specifically breaks inside an FP&A team, and what infrastructure stops the monthly scramble?"

Read more

A newcomer should start here because it pairs a recognizable failure story with a named deliverable—the seven templates—and shows the diagnosis-plus-asset pattern repeated in Bojan Radojicic's posts.

Bojan Radojicic opens with an audit of an FP&A team working 70-hour weeks.

  • They were smart and hardworking, but reporting was a mess and every month was a fire drill.
  • The post lists the symptoms: static spreadsheets, broken VLOOKUPs and manual variance comments that took three days to write.
  • When the CFO asked for a 12-month rolling forecast, the room went silent: no model existed, so the team had to build one from scratch.
  • The post calls this the hidden cost of manual finance: hiring top talent, then using them as data entry clerks.
  • With 15 years in finance, Radojicic argues that the difference between a good team and a world-class team is not the software they buy but the standard of the templates they build.
  • Teams should not reinvent the wheel every Monday.
  • The post names seven must-have templates every FP&A professional should master, from 3-statement models to driver-based forecasting, and says that with these ready, a fire drill becomes a 10-minute update.
  • It links to a download of the templates.

For brands planning a campaign

The template pack is ready to become a campaign asset: a co-branded or sponsored resource for FP&A leaders that positions a software vendor alongside driver-based forecasting and rolling forecasts.

  • The post supplies the pain language buyers use: fire drill, static spreadsheets, broken VLOOKUPs and three-day variance comments.
  • A finance software company can echo that language in a co-marketing landing page or webinar and offer a concrete template download instead of a product demo.

Survey of 102 finance leaders on accounts-payable automation

Answers the question "how do finance leaders actually describe their accounts-payable gap, and what does the event side of this audience look like?"

Read more

A newcomer should start here for quantified pain points with a stated sample size, plus a clear view of the conference promotion alongside Bojan Radojicic's finance commentary.

The post leads with a survey result: only 18% of SMB finance leaders are actually happy with their AP solution.

  • It says 102 finance leaders, mostly CFOs, VPs and finance directors, were asked how they run accounts payable today.
  • The findings: 33% still run AP manually or inside their ERP with no dedicated tool; 50% say their current solution could be better or that they are not satisfied; 65% want their provider to bring more automation and AI; and approvals and payments and invoice capture tie as the biggest automation opportunities, at 22% each.
  • Bojan Radojicic shifts from the tool question to the function question: AP is often the first place finance teams feel the automation gap, but rarely the only one.
  • The real question is how to build a finance function where automation and AI work end to end.
  • The post promotes CFO AI Nexus as built for that, describing two days of practical sessions, live demos and conversations with 300+ CFOs, six stages, 20 conference sessions, 100% virtual, October 20-21, 10 am to 4 pm ET, limited regular tickets and a registration link.

For brands planning a campaign

The survey gives a vendor ready-made statistics for a co-marketing campaign: 18% satisfaction, 33% still manual, 65% wanting more AI, and two tied automation opportunities at 22% each.

  • The event promotion also identifies a venue.
  • A finance software company could approach the CFO AI Nexus sessions for a sponsorship, speaking or demo slot aimed at the same FP&A and CFO audience.
Sources for this section

Topics and approach

Posts cited for each topic
Recurring approach: diagnose manual pain, then add templates, automation, and guardrails3
Building custom finance reporting apps with AI coding tools1
FP&A templates as infrastructure, not recurring busywork1
Accounts payable automation: survey data and event promotion1

Building custom finance reporting apps with AI coding tools

In one post, Bojan Radojicic describes how a finance leader and small team can build a reporting app using Claude Code, Git/GitHub, and Cloudflare.

Read more

The app would pull trial balances, budgets, and forecasts from a Drive folder; build P&L, balance sheet, and cash flow in management format; compare actuals against budget, forecast, and last year; and draft variance commentary.

  • The post stresses controls: code calculates every figure and reconciles it to the trial balance, AI writes only the words, line owners review and edit every comment, and a developer reviews the code and infrastructure before real data is used.
  • It also lists company login with MFA, role-based access, and a full audit trail as mandatory, and estimates a realistic first version at 10 to 14 weeks.

Plain-English app rules, code-calculated figures, AI-written commentary, review by line owners, and technical review before production data is used.

The post warns that speed without control is risky: real data should not be used until a developer has reviewed the code and infrastructure.

For brands planning a campaign

A finance software company can build a practical, control-aware campaign around safe AI-assisted reporting, implementation checklists, security and review gates, and realistic timelines. The strongest hook is not AI hype but a process that separates calculation, commentary, and accountability.

Examples: Source 1

FP&A templates as infrastructure, not recurring busywork

Another post describes an audit of an FP&A team working 70-hour weeks with static spreadsheets, broken VLOOKUPs, and manual variance comments that took three days to write.

Read more

When the CFO asked for a 12-month rolling forecast, the team had no model and had to build one from scratch.

  • Bojan Radojicic argues that the difference between a good and world-class finance team is not the software they buy but the standard of the templates they build.
  • They point to seven must-have FP&A templates, including three-statement models and driver-based forecasting.
  • The pitch: with the right templates, a monthly fire drill becomes a ten-minute update.
  • The post offers a download of the templates.

A diagnostic audit, specific time costs, templates as the fix, and a resource download as the next step.

For brands planning a campaign

A finance software or FP&A platform can co-market template libraries, lead magnets, and webinars that help teams move from spreadsheet repair to driver-based forecasting. Show the before-and-after process and connect templates to product setup rather than offering a generic download.

Examples: Source 1

Accounts payable automation: survey data and event promotion

A third post presents findings from a survey of 102 finance leaders, mostly CFOs, VPs, and finance directors.

Read more

It reports that only 18% of SMB finance leaders are happy with their AP solution, 33% still run AP manually or inside their ERP with no dedicated tool, 50% say their current solution could be better or they are not satisfied, and 65% want their provider to bring more automation and AI.

  • Approvals and payments and invoice capture tie as the biggest automation opportunity at 22% each.
  • The post uses those numbers to argue that finance teams know what is broken and need a clear path to end-to-end automation, then promotes CFO AI Nexus as a two-day virtual event with six stages, twenty sessions, and 300+ CFOs.

A short survey-based hook with specific percentages, a diagnosis of manual AP, and an event registration call to action.

The automation argument is tied directly to a named conference. If the brand is not the event organizer, separate the survey findings from the event promotion.

For brands planning a campaign

A finance software company can co-brand a similar AP or finance-automation survey, use the data as an educational asset, and direct readers to a demo or event. The stats make a ready-made case for automating approvals, payments, and invoice capture; add independent value beyond reposting the event.

Examples: Source 1

Recurring approach: diagnose manual pain, then add templates, automation, and guardrails

Across the three posts, the same argument recurs: finance teams waste skilled people on manual collection, reconciliation, formatting, and commentary; the fix combines better templates, automation, and AI support with human review, security, and clear accountability.

Read more

The format is consistent too: LinkedIn text posts built on short lines, bullet lists, concrete time costs or percentages, a named pain point, a practical framework, and a resource or event link.

Pain-point diagnosis, short-form LinkedIn structure, bullet lists, concrete figures, and a clear next step or resource.

For brands planning a campaign

A brand should match this practical, control-aware tone: lead with a specific finance process problem, quantify the cost, propose a template or automation path, and include human and security guardrails. Product promotion without the operational fix would miss the approach running through the posts.

Examples: Source 1 · Source 2 · Source 3

Sources for this section

Brands and businesses

Across three posts, the brands Claude, Cloudflare and GitHub appear as the tool stack behind a custom finance reporting app, alongside CFO AI Nexus, an accounts-payable conference promoted with a registration link.

Read more

The posts also refer to “one of my companies” and to a “we” that builds FP&A templates and surveyed 102 finance leaders, without naming those businesses or stating the role involved. No post states a sponsorship, paid partnership or employment arrangement.

Anthropic Claude

Mention

Named as the tool for writing code for a custom reporting app that a finance team can build, in a post recommending a stack for automating month-end reporting.

Read more

The post presents it as a practical tool.

View example

Cloudflare

Mention

Named as the host for the reporting app behind a secure login, in the same recommended tool stack.

Read more

View example

GitHub

Mention

Git and GitHub are named as the version control tools that track every change to the app’s code, as part of a tooling recommendation.

Read more

View example

CFO AI Nexus

Disclosed partnership

The post presents survey data on accounts-payable automation, then points readers to CFO AI Nexus, a two-day virtual conference with 20 sessions for CFOs, a registration link and ticket details.

Read more

Ask whether the connection is speaking, sponsorship or another kind of relationship.

View example

Sources for this section

Topics and similar creators

Bojan Radojicic writes about where finance processes meet software: FP&A templates, reporting automation, AI-assisted commentary and accounts-payable tooling.

Read more

The three posts cover a custom reporting app built with AI coding tools and the controls that make it safe, an audit story about an FP&A team trapped in spreadsheet repair, and survey numbers on how manual accounts payable still is.

  • Read them in that order for the argument, process detail and supporting evidence.
  • Each post follows the same shape: a named pain with a cost attached, a practical fix, and a download or event at the end.
  • The creators listed below reach the same audience from different vantage points: client accounting services, capital allocation and working capital, and CFO-level investment economics.
FP&A Finance reporting automation AI in finance Accounts payable Finance templates and models Reporting controls and audit trails Building finance apps LinkedIn text posts Weekly newsletter Survey-based posts Finance leaders FP&A professionals

Anooshay Arif

Both write for finance practitioners about the manual load inside the close and what AI can take off their plate.

Read more

Anooshay Arif describes flipping the usual split—teams spend 80% of their time producing numbers and 20% explaining them—using AI to flag bank reconciliation anomalies and pattern-match the obvious 70% of AP/AR work.

  • They argue that a new CFO's first 90 days are about alignment before dashboards.
  • Bojan Radojicic makes the same case for templates and guardrails: fix the process and keep a person on the judgment.

Anooshay Arif writes from inside client accounting and outsourced finance, focusing on close, reconciliations and how a new CFO builds trust in the numbers. Bojan Radojicic goes further into the build, describing a custom reporting app, its security requirements and review gates, and offering template downloads and event registrations as next steps.

Read original · Original 2

Rajesh Viswanath

Both turn finance operating practice into short, decision-oriented arguments for CFOs and FP&A teams, using outside research to make their case.

Read more

Rajesh Viswanath draws on McKinsey material to argue that capital should go to the handful of value drivers that explain most performance variance, rather than departmental requests, and cites a PYMNTS report showing a 20-day cash conversion gap between top and bottom performers. Bojan Radojicic makes a comparable case with AP survey data and a build checklist.

Rajesh Viswanath stays at the strategy and metrics level—capital allocation, value drivers and the cash conversion cycle as competitive advantage. Bojan Radojicic stays at the process level, showing what a team builds, what rules the work must follow and how long a first version takes.

Read original · Original 2

Jeff Epstein

Both push beyond whether finance teams use AI to ask what changed as a result.

Read more

Jeff Epstein asks whether forecasting, reporting, close, collections or analysis became more productive, whether the economics moved and whether anyone can measure it.

  • They also say they changed their mind about the CFO's job being mainly to police AI spend.
  • That demand for evidence behind AI claims runs through Bojan Radojicic's rule: code calculates every figure and reconciles to the trial balance, while AI only writes the words.

Jeff Epstein writes from a CFO and investor vantage, weighing AI returns across a portfolio and using live events to gather insights from finance leaders. Bojan Radojicic writes as a practitioner, explaining one build at a time with the security, review and approval detail needed when working near real data.

Read original · Original 2

Sources for this section

Audience

For a finance software company targeting FP&A leaders, treat Bojan Radojicic as a LinkedIn-first candidate for finance-automation and FP&A-template messaging, not as a verified route to a measured FP&A-leader audience.

Read more

Their posts speak to that world: one describes a CFO asking how to automate reporting work between systems and outlines a custom reporting app using Claude, Cloudflare, and Git/GitHub; another describes an FP&A team working 70-hour weeks and promotes seven must-have FP&A templates; a third reports a survey of 102 finance leaders on accounts-payable automation.

  • The dated platform audience figures are 335,767 LinkedIn followers on 2026-10-08 and 843 Instagram followers on 2026-10-11.
  • The LinkedIn scale makes a test plausible, but the posts do not establish how many followers are FP&A leaders, CFOs, or in target geographies.
  • Before buying, ask for recent LinkedIn audience survey results or platform demographics by job role or seniority and geography, plus recent post performance on comparable finance-automation and FP&A-template topics.

LinkedIn followers

335,767

LinkedIn account metadata · 2026-10-08

Instagram followers

843

Instagram account metadata · 2026-10-11

Sources for this section

Partnership options

The three available posts promote Bojan Radojicic’s own channels rather than third-party deals: a Saturday newsletter pitched to finance readers, a set of FP&A templates offered as a download, and a virtual CFO conference with registration and ticket details.

Read more

None names a brand partner, rate, placement specification, or partnership terms.

  • One post claims the newsletter has 90,000 finance readers, making it the clearest owned audience a finance software company could approach.
  • Before committing budget, ask whether the newsletter accepts paid placements, sponsored sections, or co-branded content; what each format includes; who approves the copy; and what the audience figures are based on.
  • No official sponsorship inquiry route was verified.
Sources for this section

Campaign fit

A campaign to shortlist

A finance software company selling FP&A planning and reporting tools wants to reach FP&A leaders through a co-marketing campaign on finance automation and FP&A templates.

Read more

Recommended, subject to audience and sponsorship checks before budget is committed.

  • The posts already address that audience.
  • One diagnoses an FP&A team working 70-hour weeks: static spreadsheets, broken VLOOKUPs, variance comments that took three days to write, and a 12-month rolling forecast the team had to build from scratch.
  • It ends with a seven-template download covering three-statement models and driver-based forecasting.
  • Another describes a finance leader and a small team building their own management reporting app with Claude Code, Git/GitHub and Cloudflare.
  • The app pulls trial balances, budgets and forecasts from a Drive folder, assembles the P&L, balance sheet and cash flow in management format, compares actuals with budget and forecast, and drafts variance commentary with AI for line owners to review before it reaches the CFO.
  • A third reports a survey of 102 finance leaders, mostly CFOs, VPs and finance directors, on accounts payable: 33% still run AP manually or inside an ERP, 65% want their provider to bring more automation and AI, and approvals and payments and invoice capture tie as the biggest automation opportunity.
  • The commercial shape also suits a vendor.
  • Each post ends with an asset a software company could co-brand or sponsor: a template pack, a survey, a build walkthrough or an event registration.
  • The repeatable format—named pain point, short lines, bullets, concrete time and percentage figures, one link—gives a vendor a natural next step after a template download or readiness checklist without changing the register.
  • The listed audience data comprises a LinkedIn follower count of 335,767 observed 2026-10-08 and an Instagram count of 843 observed 2026-10-11; neither identifies how many followers are FP&A leaders, CFOs or in the vendor's target geography.
  • The creator says the newsletter reaches 90,000 finance readers, but that claim is not verified in the posts.
  • Ask for a recent audience breakdown by role, seniority and geography, the basis for the newsletter figure, and a written sponsorship menu with rates, formats, copy-approval process and placement specifications before treating this as a purchasable placement.

When to choose a specialist

A developer-tools company selling CI/CD, infrastructure-as-code and cloud deployment wants a creator partnership reaching platform engineers who influence tooling purchases.

Read more

Do not use this creator for the campaign.

  • One post names Claude Code, Git and GitHub, and Cloudflare hosting, which can look like an engineering-audience match at a glance.
  • In context, those tools serve a finance outcome.
  • The reader is a CFO or finance leader whose month-end close takes six or seven days, five of them spent collecting, reconciling and formatting numbers.
  • The controls are accounting controls: code computes every figure and reconciles it to the trial balance; AI writes only the words; line owners review and edit every comment before it reaches the CFO; and the process includes company login with MFA, role-based access, a full audit trail, and review-and-approval options.
  • A developer enters the post once, to inspect the code and infrastructure before real data goes in—a finance governance step, not an engineering-buyer pitch.
  • The posts do not address deployment pipelines, developer experience, platform-team workflow or an engineering audience.
  • The other two posts stay in the same lane: an FP&A template pack built around three-statement models and driver-based forecasting, and an accounts-payable survey tied to a virtual CFO conference.
  • Developer-tools messaging would reach finance practitioners, while the published follower counts provide no role-level breakdown and no indication of engineering reach.
  • A campaign would require the creator to take up a topic the posts do not address, a different proposition from co-marketing that the available content does not support.
A worked campaign example

Worked example: a “month-end reporting gap” co-marketing campaign for the finance software company.

Campaign angle. Lead with a failure the buyer recognizes, not with AI. Use the costs already described in the posts: a close of six or seven days, five spent collecting, reconciling and formatting; commentary written late at night under pressure; management seeing the story days after the numbers; and strong analysts used as data clerks. That framing can anchor the campaign's first post and landing page.

Lead asset. Build a co-branded reporting-automation readiness pack, modeled on the template download in the posts. It could include a short checklist for finance leaders to score their close against, using the symptoms already named (static spreadsheets, broken VLOOKUPs, three-day variance comments, no rolling-forecast model), plus a one-page blueprint. The blueprint would cover the three rules for trustworthy automation (code calculates and reconciles every figure, AI writes only the words, and line owners review every comment before it reaches the CFO), the security list (company login with MFA, role-based access, audit trail, review and approval), and the realistic 10-to-14-week first-version timeline.

Second asset. Host a recorded or live build walkthrough demonstrating the vendor's product against the same guardrails, with a developer reviewing code and infrastructure before real data is used. Show the vendor's tool inside a governed process, not as a general AI claim.

Survey angle. The accounts-payable figures in the posts come from the creator's own survey and appear alongside promotion of a named conference. The vendor should either co-produce a new survey and jointly own the data, or cite the existing figures with clear attribution and add original analysis. Reposting the numbers as the vendor's own would be misleading.

Distribution. Use one LinkedIn text post in the creator's established format (short lines, bullets, concrete time and percentage figures, a single link), a newsletter mention if a paid placement exists, and a sponsor, speaking or demo slot at a finance event of the kind the creator already promotes. Treat the newsletter placement as an option to price, not a confirmed channel.

Vendor contribution. Supply subject-matter review of the pack, a sandbox environment for the live demo, and security and legal sign-off on the guardrail claims. Do not promise pipeline numbers or role-verified reach without an audience breakdown.

Buyer path. Drive readers from the template and checklist download to a self-scored readiness result, then to a demo. Before proceeding, ask which paid formats exist, what each placement includes, who approves copy, what the audience figures are based on, and whether a sponsorship package is available. The posts do not describe a purchasable package.

Sources for this section

Who else to consider

Anooshay Arif

Choose Anooshay Arif over Bojan Radojicic when the campaign is about changing how senior finance people spend their time, not promoting a template download.

Read more

The posts describe a target ratio: 80% of finance team time producing numbers and 20% explaining them, with a plan to flip it.

  • They offer concrete automation scenes to sponsor: bank reconciliations where AI flags anomalies and a person approves every one; AP and AR where pattern matching handles the obvious 70% and people handle the messy 30%; variance commentary where AI drafts and a person who knows the client's business refines; and a reporting package where data assembly is automated while a person writes the narrative.
  • A second post argues that a new CFO's first 90 days should fix alignment before metrics, because sales, product and go-to-market teams often disagree on ARR, bookings and spend, and dashboards only work once the numbers are trusted.
  • This suits a campaign selling judgment, review and alignment around automation, or a services layer alongside software.

The tradeoff is distribution and campaign machinery.

  • The posts contain no template download, survey, event promotion or build walkthrough, so a vendor would need to create the lead asset and reader path rather than plug into an existing funnel.
  • Their argument-led point of view is useful for positioning but offers less ready-made material for a gated checklist or product demo.
  • Ask for audience size, job-title breakdown and sponsorship availability to verify reach and placement.

Examples: Source 1 · Source 2

Rajesh Viswanath

Choose Rajesh Viswanath over Bojan Radojicic when the campaign targets CFOs and FP&A leaders making capital-allocation and working-capital decisions, and the vendor sells driver-based planning, cash visibility or forecasting.

Read more

One post argues that traditional budgeting fails at capital allocation, not budget building: departments submit requests, finance decides who gets what, and the better question is which investment moves the most important enterprise value drivers.

  • It names SaaS drivers such as net revenue retention, CAC payback, pipeline conversion and gross margin, and manufacturing drivers such as capacity utilization, yield, inventory turns and on-time delivery, then connects them to driver-based planning.
  • A second post reframes the cash conversion cycle as a competitive advantage, citing a PYMNTS Intelligence report that top performers convert cash in 24.2 days versus 44.4 days for lower performers.
  • The argument is that the gap comes from visibility across procurement, operations, suppliers and finance.
  • This fits software that connects operational and financial data, or a campaign seeking a CFO-level strategic frame rather than a hands-on template.

The tradeoff is originality and campaign ownership.

  • Both posts build on outside research—McKinsey on value drivers and PYMNTS Intelligence on the cash conversion cycle—so a vendor would need to license and cite the research, then add original analysis.
  • The posts offer no original survey, downloadable template, event or product walkthrough, so the co-marketing asset would need to be built.
  • Ask for audience size, role breakdown and sponsorship availability to assess reach and commercial fit; the posts are shorter arguments rather than teaching sequences.

Examples: Source 1 · Source 2

Jeff Epstein

Choose Jeff Epstein over Bojan Radojicic when the campaign needs CFO-level credibility on AI economics or an event-led activation rather than an evergreen template.

Read more

Jeff Epstein writes from both sides of technology investment: as a former CFO at Oracle and other companies, and now as an investor at BVP.

  • One post asks what actually changed when finance teams use AI in forecasting, reporting, close, collections or analysis—whether teams became more productive, economics changed, decisions got faster or better—and whether any of it can be measured.
  • Another says the CFO's role in AI has shifted from controlling spend to asking what AI does to margins, pricing, retention and collections.
  • It cites a Bain estimate of $4.7 trillion in global profit at stake from AI between 2025 and 2035.
  • Both posts promote Finance Exchange in San Francisco on October 15, one with Priya Rajan, giving a vendor a natural event-sponsorship or speaking angle tied to a senior finance audience.

The tradeoff is that the posts are opinion and event promotion, not an implementation asset.

  • They offer no FP&A template pack, survey, build walkthrough or step-by-step automation guide to co-brand.
  • A vendor selling FP&A planning or reporting software would need to supply the practical asset and use Jeff Epstein's posts as the credibility layer or event draw.
  • The event tie makes the campaign time-bound and likely more expensive or complex than a download.
  • Ask for a sponsorship menu, rate and audience breakdown to assess commercial availability and role-level reach.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Campaign brief template (blank)

Completed brief: finance software vendor — FP&A reporting automation

Completed brief: accounts payable automation vendor — survey-led campaign

Completed brief: developer-tools vendor — rejected, with the reason recorded

Sources for this section

Research methodology

  • This profile describes three full LinkedIn posts by Bojan Radojicic: one on a custom finance reporting app built with Claude Code, Git/GitHub and Cloudflare; one on FP&A template pain, rolling forecasts, and spreadsheet-heavy reporting; and one on survey findings about accounts-payable automation.
  • No publication dates appear with the posts.
  • The posts here are short-form LinkedIn text; longer articles, video or audio transcripts, event sessions, and the Instagram account are not covered.
  • The posts do not establish whether a signature book, show, business, or earlier body of work is central to name searches; that remains an open question.
  • No sponsorship formats, rates, copy-approval details, or audience breakdown by role, seniority, or geography are published in the posts here.
  • The overview, ideas, relationships, discovery, and fit sections are reflected in this metadata.

Brands they talk about