Services
Software
Scope
Planning, design pipeline, approvals, publishing
Year
2026
Tools
Supabase, Meta Graph API, Figma, Higgsfield, Claude
The Content Engine runs the Colrosa Studios Instagram and Facebook accounts. Every Thursday it plans the next week’s posts, builds each one from an approved design library, checks them and lines them up for Max to approve.
Approved posts go out at their set times, and every post is measured so the results shape the week after. It took over the making, checking and scheduling Max used to do by hand.
Colrosa Studios needs to post every day to be found. Making, checking and scheduling a week of posts by hand took hours that should go on client work.
A loop that runs every week. Each slot has a job, posts are built from an approved design library, and nothing goes out until it's approved on desktop or phone.
01
Plan on Thursday
At 09:00 every Thursday it plans the next week. Each slot has one job, such as reach, saves, comments, shares or enquiries, and about 15% of picks try something less proven.
02
Build from the library
Posts reuse approved designs first. New ones are built from Figma templates, with images made in Higgsfield when a post needs one.
03
Check every post
Scripted checks run first, then a visual review. A post that fails is rebuilt up to twice, then flagged.
04
Max approves
The week waits on the Social page in Studio OS or on his phone. He approves, edits captions or rejects in one sitting.
05
Publish and measure
Approved posts are published through Meta’s API, which is checked every 10 minutes for posts that are due. Each post is measured at 1, 3, 7 and 28 days.
06
Tune on Monday
Results change what the planner favours next. A slot’s posting time moves by up to two hours when another time does better over four or more posts.
posts published
