Content

Safety: no auto-publish to the public site. Publishing requires a PUBLISH_CONTENT approval. No fake engagement. Distribution is Postiz/mock only — codeloop.ba CMS is never modified from this queue.

Masters: 3 · Variants awaiting review: 2 · Queue: 3 · Snapshots: 1

Master content

TitleSourceStatusKey pointsOwner
Custom software for hospitality BA — SEO briefseo briefawaiting approvalDemand gap vs competitors; ICP hotels/villas BA; no existing cluster page on codeloop.ba.nejra
How CodeLoop runs internal toolsarticlescheduledSelf-hosted ops stack; Coolify + Postgres; human approvals for Level-3 actions.mahir
Case note: product engineering partnershipcase studypublishedLong-term delivery model; BA timezone overlap; measurable product outcomes.mahir

Variant review

Channel-native copy — LinkedIn ≠ Instagram paste. Approve / reject / request changes before schedule.

linkedin · postawaiting approval

Custom software for hospitality BA — SEO brief · nejra

Most hotel operators in BiH still stitch bookings, ops, and guest messaging across three tools.

We wrote a short brief on where custom software pays off vs off-the-shelf — without the doorway-page spam.

If you run hospitality in BA and want a calm technical partner, comment or DM.

#Bosnia #HospitalityTech
instagram · carouselawaiting approval

Custom software for hospitality BA — SEO brief · nejra

Slide 1: Hotels in BiH — tools that don’t talk to each other
Slide 2: What “custom” actually means (narrow, owned, maintainable)
Slide 3: When SaaS is enough (and when it isn’t)
Slide 4: How CodeLoop partners — not a content factory
Slide 5: CTA — link in bio / DM “hospitality”
linkedin · postapproved

How CodeLoop runs internal tools · mahir

We run our own internal OS: private Postgres, Valkey queues, Coolify deploys, and Level-3 approvals before anything touches production.

Not because it’s trendy — because client work and our own ops share the same trust bar.

Thread-style notes in the comments if useful.
linkedin · postpublished

Case note: product engineering partnership · mahir

A quiet case note: multi-quarter product engineering with a BA-based team — overlap hours, owned backlog, no vanity “AI article farm.”

Results lived in the product, not in fake engagement screenshots.

Schedule

ScheduledChannelProviderStatusMasterErrors
2026-08-21T18:30:00.000ZlinkedinpostizscheduledHow CodeLoop runs internal tools
2026-08-20T09:00:00.000ZlinkedinmockpublishedCase note: product engineering partnership
instagrampostizfailedCustom software for hospitality BA — SEO briefPostiz mock: channel not connected (no credentials required for Control)

Performance

Metrics snapshots from mock/Postiz — winner and repurpose hints only; no fabricated engagement.

MasterChannelImpr.ClicksEngagementWinner / hint
Case note: product engineering partnershiplinkedin4203118 likes · 4 comments · 2 sharesWinnerWinner: expand into a short newsletter + IG carousel (facts only, no fake engagement).