Two weeks ago I shipped Beam — a tool I built to save myself an hour a day publishing video to four platforms. Today I am shipping the second version, with two changes that came entirely from people who started using it. Before I tell you what changed, here is the original story, in case you missed it.

How it started

On April 13, while finishing a pull-day workout 151 days out from Leh, I posted a reel about a small utility I had been building. The reel was supposed to be about training. It became about something else entirely.

T-151 days to Leh. Pull day done.
Reel 01 — The Origin
T-151 days to Leh. Pull day done.
13 April 2026 · Can & Able

"Last week I was building a simple utility — publish videos on LinkedIn, YouTube and Meta in one go. The utility now schedules and publishes across all platforms. But it's also storing the original video on cloud storage before publishing. And that is solving a problem you don't even know exists."

The next morning, on T-150, I implemented Beam on shamkamboj.com. Two years of content — Average to Epic, Can & Able — pulled back to my own domain, my own cloud, my own files. I became my own first customer.

I Became My Own Client | Beam — Own Your Content
Reel 02 — The Implementation
I Became My Own Client. Beam — Own Your Content.
14 April 2026 · Can & Able

"Yesterday I showed you Beam. Today I implemented it on shamkamboj.com. Two years of content — Average to Epic, Can & Able — all of it back on my own domain. My own cloud. Mine."

That same day, I wrote the launch article — I Built a Tool to Save One Hour a Day. It Accidentally Solved a Problem I Didn't Know Existed — explaining why content ownership matters more than the hour Beam saves. If you have not read it yet, that is the foundation for everything below.

What people asked for

Within the first week of release, two things came up. Both from people actually using the tool.

One. X (Twitter) was missing. Beam was publishing to YouTube, Instagram, LinkedIn, and Facebook — but not X. Most users wanted X in the same flow.

Two. People were posting impromptu from their phones. A reel from a meeting, a clip from a site visit, something they shot in the moment. Those posts were going up directly — bypassing Beam — and then not appearing in the Beam dashboard. Their content history was suddenly fragmented again.

Both problems were real. Neither was something I had thought about during the original build. They came from actual use. That is the only feedback that matters — feedback from people who chose to use the thing.

What changed in version 2

X publishing is live. All five platforms — YouTube, Instagram Reels, LinkedIn, Facebook Pages, and X — now publish from the same screen, in one action. Same caption flow. Same scheduler. Same dashboard.

One note on X. The X API moved to a pay-per-use model earlier this year. Each tweet posted via the API is billed by X directly to your account at roughly $0.01 per post. Beam includes the integration in every plan; the X API charges go to X, not us. For most people that adds up to a few rupees a month. The other four platforms remain free.

Catch-up sync is live. If you post directly from your phone or tablet, Beam now picks up the post automatically. The metadata — title, description, link — lands in your dashboard within minutes. Your post history stays unified, even when the upload itself did not go through Beam.

For posts that come in via catch-up sync, the original video file lives on the platform you uploaded to. If you also want the file backed up to your own R2 bucket, open the post in Beam, choose your local copy of the MP4, and hit upload. Beam renames the file to match the post and pushes it to R2. The metadata is automatic. The file backup is one click away when you want it.

I shipped both of these today, two weeks after the original release. I told the story in a reel this morning.

Beam — X is live, plus catch-up sync. Built from your feedback.
Reel 03 — The Iteration
Beam — X is live, plus catch-up sync. Built from your feedback.
26 April 2026 · Can & Able

"A few weeks ago I told you about Beam. The one missing was X. That's working now. Another problem came up — posts made directly from devices were missing from Beam's dashboard. That's sorted too. Five platforms. One place."

Why this matters more than the features

I shipped this in two weeks because I am using Beam every day, the people who took early access are using it every day, and we were all hitting the same gaps. The X integration took longer than the rest because of how their API changed this year — but it shipped. The sync feature took less time because the architecture was already designed to support it.

This is the loop I trust. Build it. Use it. Find the gaps from real use. Fix the gaps. Ship again. The same loop applies to everything — businesses, training, content systems. There is no other way.

The pricing

Same three plans. All features included in every plan. The only difference is how you want to pay.

Plan Price Effective Notes
Monthly ₹499/mo ₹499/mo + ₹1,000 setup fee. Cancel anytime.
Quarterly ₹1,397/qtr ₹466/mo No setup fee. Save ₹400/year.
Annual ₹4,999/yr ₹416/mo No setup fee. Save ₹989/year.

X API charges (about $0.01 per tweet) are billed by X directly and are separate from Beam's plan price.

If you want to try it

The product page is at fidus.one/apps/beam — full feature list, FAQs, and the contact form to get started.

Or, if you would rather just talk to me first — start a conversation.

And if you have not read the launch article from April 14, that is the philosophy this whole thing is built on — read it here.

Can & Able. Body for endurance. Systems for scale.