FB & IG Proof of Concept: Proposal for Russ Climie

01 — The Trial

This is a proof of concept, not a promise.

You run it on your own accounts, on your own posts, on your own schedule. Then you decide.

You've been getting LinkedIn publishing out of the tool for a while now. Facebook and Instagram never got connected, and that sat longer than it should have. That's on me, and I appreciate you checking back in rather than writing it off.

So I'm not going to ask you to take a feature request on faith. The point of this piece of work is to put a real answer in your hands: connect Facebook and Instagram, publish real posts through the tool on your own schedule, and see for yourself whether it holds up under normal use. If it does, you'll know it because you watched it happen, not because I told you.

That's the whole reason it's shaped as a trial rather than a launch. One contained piece of work, one clear thing to judge, and nothing bigger committed to on either side until you've judged it.

02 — What's Already Built

The engine is written. Proving it live is the work.

Your tool was built from day one to publish to more than one platform. The Facebook and Instagram code exists and has never once been run against Meta's live servers.

Being honest about where the line falls: the publishing engine, the token storage, and the Facebook and Instagram posting code all already exist in your tool. What has never happened is a single real post going through a live Meta app. Closing that gap is exactly what you'd be buying.

What is genuinely done

The tool speaks four platforms, not one. Facebook and Instagram already have their connect buttons, their stored credentials, and their posting calls written and tested. This was never LinkedIn-only code waiting to be widened.

What is genuinely not

Those tests prove the tool asks Meta the right question. They can't prove Meta answers. Nothing here has ever touched a live Meta app, a real Facebook Page, or a real Instagram account.

The one flaw I already found

Facebook keeps a connection alive differently than LinkedIn does, and the current code does it the LinkedIn way. Left as is, your connection would likely work once and then quietly stop. That's a real fix, and it's in scope.

I'd rather show you that third card than leave it out. It's the kind of thing that looks like nothing on a proposal and turns into you wondering in six weeks why your posts stopped going out.

03 — Scope

What actually happens.

Three pieces of work, plus two small things on your end.

The work

Connect, publish, and keep it working

Connect the Tiberius Images Facebook page and Instagram account to your web tool through Meta's app permissions.
Publish directly from the tool to Facebook and Instagram, the same way LinkedIn works today.
Fix the connection-refresh problem described in Section 02, so you're not hitting expired-connection errors down the road.
Post through to your real accounts and fix whatever the live Meta API rejects that the current tests can't predict.

On your endGrant app access to FB page + IG account On your endConfirm IG is a Business or Creator account

If your Instagram is already linked to the Tiberius Facebook Page as a Business or Creator account, there's nothing to do on that front. Meta requires that link before any tool can post, so it isn't something specific to this build.

One honest limit: Instagram posting through this integration is photos only. No video, no Reels. If that's something you want later, it's a separate and larger piece of work, not part of this scope.

04 — What Working Looks Like

A concrete bar, not a vague one.

Here's what "it works" actually means, so you're not guessing what to judge it against.

You post it, it shows up

Publish from the tool, and the post appears on your Facebook Page and Instagram feed, the same way it already does on LinkedIn.

It stays connected

No re-authorizing every few weeks. The connection-refresh fix is what keeps it alive on its own.

You judge it on real use

Not a one-time demo. Run it on actual posts, over actual weeks, and see whether it earns a place in how you already work.

If it clears that bar, you have something you can rely on and something you can point at. If it doesn't, you'll know that too, and you'll know it early and cheaply rather than after committing to something larger.

05 — Timeline

Fast on my end. Meta is the wildcard.

One to three focused engineering days. The calendar time around it depends on Meta, not on me.

Engineering time

One to three focused days once you've granted app access: connecting the platforms, fixing the refresh problem, and testing against your real accounts.

Calendar time

Realistically one to two weeks end to end, once Meta's dashboard setup and first-pass testing against a live account are folded in.

The one thing genuinely outside either of our control: Meta sometimes requires a Business Verification review for this permission set. If it's not required, the window above holds. If it is, that adds real time on Meta's queue, not mine. I'll know which path we're on once I'm in the dashboard, and I'll flag it immediately if it's the slower one.

I'd rather tell you that up front than promise a date I can't fully control.

06 — Investment

What the number is actually for.

One number, one build, one real trial on your own accounts.

Total for the FB/IG proof of concept

Covers the Meta app connection, Facebook and Instagram publishing, the connection-refresh fix, and posting through to your real accounts until it holds. One-time cost, with no ongoing fee for this piece.

$6,000

Here's the honest argument for that number, since I've never quoted you anything before and you have nothing to compare it against.

It's priced on the unknown, not the typing

Writing the code isn't the risky part, because most of it is written. The risky part is the first real conversation between your tool and Meta's servers, where an integration either works or reveals a week of small, specific problems nobody can predict from the outside. That's what this buys: someone taking that on until it's finished.

It's one number, not a meter

No hourly clock, no change order if Meta's setup turns out to be fussier than it looks. You know the cost before you decide, and the uncertainty above is already priced into it.

What it's worth after

Two more places your work publishes automatically, permanently, at no cost per post. And a straight answer, from your own accounts, to whether this tool is something worth building further on.

This is separate from the daily content emails, which have never been billed and aren't part of this scope. That's a conversation I owe you separately, and I'm not folding it in here.

07 — Next Step

Two things from you, then I start.

Nothing complicated: a couple of permissions and we're moving.

Grant app access

Give my Meta app access to the Tiberius Facebook page and Instagram account.

Confirm the IG account type

Make sure Instagram is linked as a Business or Creator account to the Facebook Page. If it already is, you're done here.

Happy to hop on a call first and walk through any of it if that's easier than doing it cold. Otherwise, once access is granted, I get to work.

Where This Could Go

If it holds up, this is also your proof.

Back in February you floated selling this same tool to your own clients. I never gave you a real answer. I want to now.

You can't sell your clients on a tool you haven't seen hold up in your own hands. That's exactly what this trial gives you: real posts, on your own Facebook and Instagram, over real time. If it works the way it's supposed to, you're not just done with this. You're holding the evidence for the bigger idea you brought me.

I've been thinking about the shape of that since you raised it, and I'd rather bring it up myself than wait for you to ask again. No numbers here, no pitch. Once this ships and you've had a chance to run it, let's sit down and actually talk through what it could look like.