4-Week Content Calendar + Approval Workflow

Posture: quiet, Page-first. Goal of month one: establish the voice, not chase reach. Cadence: LinkedIn 2×/week (Tue + Thu, ~8–9am CT). X stays dark until Ibrahim activates it separately.

Operating rhythm (Ibrahim's call, 2026-07-24)

• Manual first. No scheduler for now; posts go out by hand Tue/Thu mornings. Third-party tools (Buffer etc.) get evaluated later, once the manual habit is proven.
• Comments are the distribution. 5 substantive comments per week, every week, protected ahead of the posts themselves. Habitats: oilfield ops voices, credit risk and portfolio ops, AP/AR and fintech vendor comment sections (pre-qualified by frustration). Never pitch in comments; add something specific or say nothing.
• Posting continues 2×/week past week 4. Batch 02 keeps the cadence; week 4's "engagement only" framing is replaced by comments-every-week plus posts.

Follow invites (250/month) — how the mechanic works

• Page admin view → "Invite connections": invite personal 1st-degree connections to follow the Page. 250 credits/month per Page, refreshed monthly; credits return when someone accepts, so acceptances are free.
• Typical acceptance for a relevant network: 30–50%. The only free bootstrap a zero-follower Page has.
• Disclosure cost: the invite arrives as a notification from Ibrahim by name. This is the one Page action that publicly links his identity to the venture.
• Options: (a) hold until employer disclosure is safe, (b) selective list only — industry peers and credit/fintech contacts outside the employer's orbit, (c) all-in. Decision pending Ibrahim; default is (b) if he wants momentum without full exposure.

Week 1 — Arrival

• Tue: Post 1 (quiet launch) — pin it
• Thu: Post 2 (the Friday backlog)

Week 2 — Ground truth

• Tue: Post 3 (the failure mode nobody demos)
• Thu: Post 4 (how a review queue should work)

Week 3 — Proof discipline

• Tue: Post 5 (five questions that end an AI vendor demo)
• Thu: Post 6 (what the audit actually is, soft CTA)

Week 4 — Engagement, not broadcasting

• No new posts. Comment thoughtfully on 3–5 target posts/week from the Page (oilfield ops, energy finance, credit risk voices). Drafts for each comment come from me first.
• Review: what got impressions, what got profile visits, what felt off. Decide batch 02 from evidence.

Approval workflow (once Buffer is connected)

1. I stage each post in Buffer as a draft via API.
2. Ibrahim reviews in the Buffer app, edits freely, taps approve/schedule.
3. Buffer publishes. Nothing goes live any other way.

Engagement targets (quiet list, to refine)

• Oilfield service operations leaders posting about field tickets / invoicing pain
• Credit risk and portfolio ops voices in fintech
• Energy-adjacent finance/automation commentators
• Rule: the Page comments only where we can add something specific. Never pitch in comments.

Batch 02 seeds (already in brand material)

• Fable research notes: "Failure modes of document extraction under rate-table drift", "Quiet interfaces"
• Careers-adjacent: "Sit closer to the fire." (only if/when hiring is real)
• Audit FAQ follow-ups based on Week 1–3 replies