See what Siddo has done in 3 days.
Proposal reviews came in as dozens of WhatsApp voice notes and screenshots.
One page: tap the spot, speak, send. The review lands ready to work from.
15 Oct · Solar Horizon · 25 min to working · How it was built
Meeting notes scattered across email.
Every call, its notes and the full transcript, in one place.
15 Oct · Solar Horizon · 34 min to working · How it was built
The tariff, USEP, weather and news were checked in four different places.
One live screen for the team, refreshed every 30 minutes, readable in under a minute.
15 Oct · Solar Horizon · 20 min to working · How it was built
Past proposals were spread across folders, revisions and drafts.
Every final proposal in one list, one download each, about 60% lighter without losing a pixel.
15 Oct · Solar Horizon · 23 min to working · How it was built
Adding someone to the team meant sharing a password over chat.
An email invite; they choose their own password, resets come by email and Sid is alerted.
15 Oct · Solar Horizon · 59 min to working
Each review had to be moved to the computer by hand.
One double-click brings every new review and its voice notes down, ready to transcribe.
15 Oct · Solar Horizon · 7 min to working · How it was built
Mail had to be copied in and out of the model by hand.
The model reads the inbox and writes drafts; nothing is sent without a yes.
15 Oct · Studio · 5 min to working · How it was built
Every change made was scattered across days and chats.
The engine: every pressure point and its fix, live, with the full log behind it.
15 Oct · Engine · 6 min to working
Thirty voice notes, one at a time: fifteen minutes gone.
Drop them all in together. They're transcribed in one go.
14 Oct · Studio · 32 min to working · How it was built
Checking that every line on the site was Sid's own meant reading page after page.
Copy: every line listed, ticked or changed by voice, and tracked as his or generated.
14 Oct · Studio · 26 min to working · How it was built
A separate login for every site.
One sign-in for all of siddo.in, and a live status when Sid is at work.
14 Oct · siddo.in · 37 min to working
Sharing the work meant screenshots and explanations spread across chats.
One front door with live windows into every project.
14 Oct · siddo.in · 24 min to working
Visitors kept seeing old versions after an update.
Every file is stamped with its contents on deploy, so changes show straight away.
13 Oct · Hosting · 7 min to working · How it was built
What changed each day was lost in the scroll.
A daily log written as the work happens, plus a view of how each system grew.
13 Oct · Engine · 13 min to working
Short edits meant opening heavy desktop software.
A video editor in the browser: contact sheets, select and edit, glitch joins, speed ramps.
13 Oct · Studio · 15 min to working · How it was built
Each project fought for the same timeline.
Workspaces: each with its own timeline, saves and history.
13 Oct · Studio · 23 min to working · How it was built
Compositing needed a separate program.
Layers, tracked masks and keys inside the same editor, matching the final render frame for frame.
13 Oct · Studio · 40 min to working · How it was built
Scoring a cut meant switching tools.
A music lane right in the editor.
13 Oct · Studio · How it was built
No internet meant no editing.
The whole of Studio on the computer, offline, syncing when it's back online.
13 Oct · Studio · 1 h 9 min to working · How it was built
A film's beats, shots and takes lived in different notes.
Story: beats, shots and takes in one place, versioned, with live sessions by invite.
12 Oct · Studio · 8 min to working · How it was built
Every image tried cost credits.
A free image pipeline, and a rule to ask before anything is spent.
12 Oct · Lab · 13 min to working · How it was built
A rigged 3D character took days of manual work.
From a concept sheet to a rigged character in one pipeline, checked before any credits go.
12 Oct · Lab · 1 h 24 min to working · How it was built
Every figure in a proposal was retyped on every page that used it.
Proposals built from one model: change the price and the payback, returns and schedule follow.
5 Oct · Solar Horizon
A community's tools were scattered across Discord, raid sign-ups, logs and a calendar.
One portal with Discord sign-in, a bot with slash commands, raids synced and every update announced.
27 Sep · For Instance · How it was built
The engine is built on things like Claude and all these other things. But it's how I've utilized them together and woven them in a way that not many people could think of doing.
Register interest. Tell Sid the pressure point.
Register interest