Execution Design

Round 6, Document 01: Execution Design

Author: Operations Strategist Date: April 2026 Status: Active — assigns every task to a named person, every week to a deliverable, every risk to a mitigation Input: Round 5 Product Spec + Content Pipeline + 90-Day Launch Plan + Team Scorecard & Operating Agreement

The Premise

The strategy is finished. The product spec is buildable. The content pipeline is production-ready. The 90-day launch plan tells a beautiful story of what the user experiences each week. None of it matters if the people doing the work cannot actually do the work.

Here is what we have: 0.7 FTE of internal capacity spread across two people who both have other jobs. One critical hire that has not been made. A contractor bench that is thin and partially committed elsewhere. An $82,000 budget that is front-loaded into Q2 ($37k) and then drops sharply. And a plan that requires simultaneous execution across platform engineering, content production, acquisition marketing, and organic content distribution.

This document does not ask whether the plan is good. It asks whether the plan is possible with the people and money available, and where it breaks if something goes wrong.

1. The Week-by-Week Ownership Map (Weeks 1-14)

The table below assumes Week 1 begins the third week of April 2026. Each cell describes the primary deliverable for that person in that two-week block. Dependencies are noted in brackets.

Kamran Ashrafi (Ameer + Platform, ~40% FE = ~16 hrs/week)

Samia Khalid (Acquisition, ~30% FE = ~12 hrs/week)

Content Production Lead (TBD -- hired Week 4-5)

Momina Hafeez (Shared Copywriter)

Wasif Paracha (IT/Engineering, as-needed)

Sohail/Eshail (Email Scheduling)

2. The Content Production Lead -- Make or Break

The 90-day launch plan states it plainly: "If this hire does not happen, Phase 2 does not happen. There is no workaround." The content pipeline document specifies this person works full-time on FE from their first day, producing 3-4 frame packages per day, managing a research assistant, an audio editor, and a theological reviewer. The job description calls for formal Islamic studies background, editorial experience, and familiarity with the AlMaghrib instructors.

This is an extraordinary set of requirements for a role budgeted at $48-65k/year that needs to be filled in three weeks.

What Happens If They Are Not Hired by Week 5

The plan assumes CPL starts Week 4-5 and has 30 production-ready frames by Week 9-10 for soft launch. If this hire slips:

Week 7 with no CPL: The daily practice feature has no content to deliver. Kamran finishes building the feature into an empty room. The soft launch cannot happen. Every downstream milestone shifts. The organic content engine has no raw material beyond what Samia can independently source from the existing library (possible, but at 30% FE allocation, she is producing 1 piece/day, not 3).

Week 10 with no CPL: The 90-day plan is dead. You are now in a fundamentally different timeline. The Q2 budget ($37k) has been partially spent on ads, email infrastructure, and engineering time, but the core product innovation has not shipped. The Q3 budget ($23k) cannot fund catch-up plus forward motion.

The Contingency Plan

If by end of Week 4 there is no confirmed CPL hire, activate the following immediately -- do not wait until Week 7 to acknowledge the problem:

Option A: Contract CPL at a higher rate, narrower scope. Find a freelance Islamic content curator -- someone who has worked at Yaqeen Institute, Bayyinah TV, Muslim Central, or a similar organization. They do not need to be the long-term hire. They need to produce 30 frame packages in 6 weeks. Scope: catalog audit of the top 4 courses only (Mogahed, Suleiman, Basyouni devotional, Qadhi faith), frame package writing, sequence the first 30 days. No Compare & Reflect. No 12-month calendar. Just enough to launch.

• Estimated cost: $5,000-$8,000 for 6 weeks of part-time contract work (20 hrs/week at $40-65/hr).
• Where to find them: Yaqeen Institute alumni network, AlMaghrib's own instructor assistant pool, Islamic online education LinkedIn groups, Muslim Professionals Network. Kamran and Noor should activate personal networks -- this is a relationship hire, not a job board hire.
• Timeline impact: Soft launch shifts from Week 10 to Week 12-13. Full rollout shifts to Week 16-18.

Option B: Kamran partially fills the role. This is the option the 90-day plan explicitly warns against, and for good reason. But here is what "partially" could look like:

• Kamran identifies and timestamps the top 15 Insight Frame candidates from the courses he knows best (he has presumably watched significant portions of the library as the product lead). This is 20-25 hours of focused work over 2-3 weeks -- which means his engineering build pauses or slows to a crawl.
• An Islamic studies research assistant (contracted, $28/hr) watches the remaining high-priority content and timestamps candidates under Kamran's direction.
• Momina writes the awakening text and connection prompts from Kamran's timestamps, under his editorial direction.
• The result: 15-20 frame packages by Week 10, not 30. Enough for a 2-week soft launch pilot, not a 30-day practice. The data is thinner but not zero.

Cost of Option B: Kamran's engineering build shifts by 3-4 weeks. The daily reflection feature does not ship until Week 12-13. The soft launch is Week 14 at the earliest. You are running out of Q2 budget before you have shipped.

Option C: Defer the daily practice. Fix acquisition first. If the CPL hire fails completely, the team pivots to what can be done without new content: landing page optimization, dormant reactivation, paid ad creative testing, email segmentation, and pre-renewal automation. These initiatives alone -- per the 90-day plan's estimates -- can generate $85,000-$123,000 in lifetime value. The daily practice becomes a Q3/Q4 initiative. This is not failure. It is triage.

Recommendation

Kamran should have 3 candidates by end of Week 2 and a verbal commitment from the top choice by end of Week 3. If no strong candidate exists by end of Week 3, immediately activate Option A (contract CPL) in parallel with continued search for the permanent hire. Do not wait until Week 5 to acknowledge the gap. The contract person buys time; the permanent hire builds the machine.

Noor's involvement is required here. This hire likely comes from the AlMaghrib instructor ecosystem -- someone who has studied under these scholars, knows the content, knows the audience. Noor's network is the hiring pipeline. A 15-minute call from Noor to 3-4 people in his network asking "who do you know who could do this?" is worth more than any job posting.

3. The Contractor Map

At 0.7 FTE internal, every deliverable that is not a decision, a strategy call, or a core product build must go to a contractor. Here is every piece of contracted work, mapped to timeline, cost, and sourcing.

Research Assistant (Content Catalog Audit)

Audio Editor (Insight Frame Extraction)

Theological Reviewer (Islamic Studies Advisor)

Graphic Designer (Organic Content + Marketing)

Video Editor (Organic Content Reels/Clips)

Frontend Contractor (Daily Practice Feature Assist -- Optional)

Narrator (T2 Intro Overlays)

Total Contractor Budget Estimate (Weeks 1-14)

This sits within the Q2 budget of $37,000 alongside the ad spend ($3-5k for A/B test, ongoing paid ads), email costs ($1,500), and CPL salary ($4,000-$5,400/month for 2-3 months in this window). The math is tight but workable if the frontend contractor is not needed and the CPL comes in at the lower end of the salary range.

4. The Burnout Risk

This is the section nobody wants to read. It is also the section that determines whether this plan survives contact with reality.

The Kamran Problem

Kamran is carrying four products: Faith Essentials (40%), QuranFlow, On-Demand, and org-wide IT. The FE strategy asks him to simultaneously:

• Make the CPL hiring decision (Weeks 1-4)
• Architect and build the daily reflection feature (Weeks 5-10)
• Manage contractors (audio editor, potentially frontend dev, Wasif)
• Run weekly team syncs
• Compile and present data to Noor bi-weekly
• Make the scholarship pricing decision
• Scope the onboarding redesign
• Monitor soft launch analytics
• Begin Ramadan 2027 technical planning

At 16 hours/week on FE, this is roughly 224 hours over 14 weeks. The engineering build alone is estimated at 64-80 hours. The CPL hire process is 15-20 hours. Management, meetings, and reporting eat another 30-40 hours. That leaves approximately 80-100 hours for everything else -- analytics, contractor management, scoping, QA, bug fixes, and the inevitable surprises.

What breaks first: Kamran's QF and On-Demand responsibilities. When the FE engineering build hits Week 7-8 and bugs emerge, when the soft launch needs daily attention in Week 10-11, and when a QF production issue lands on the same day -- something gets dropped. The most likely casualty is FE reporting to Noor (it gets delayed or abbreviated) or QF tasks (they slip). The second most likely casualty is Kamran's own wellbeing.

The pressure valve: Two specific actions can create breathing room:

1. Delegate the QF app revamp oversight to someone else for Q2. Granjur is doing the actual development. If there is a QF product person or a project manager at AlMaghrib who can handle the weekly check-ins with Granjur for 14 weeks, Kamran recovers 3-5 hours/week. That is 42-70 hours over 14 weeks -- enough to absorb the FE surprises.

2. Stop doing org-wide IT triage for Q2. Wasif should handle first-line IT issues for all products. Kamran should be escalation-only. If this has not been formally communicated to the org, it needs to happen in Week 1. Every hour Kamran spends resetting a password or troubleshooting a Zoom integration is an hour stolen from the most important product initiative AlMaghrib is running this year.

What Kamran should stop doing, explicitly:

• Attending any meeting that is not FE, QF-critical, or CEO-requested
• Handling IT requests that Wasif can resolve
• Optimizing or maintaining the On-Demand product (put it in maintenance mode for Q2-Q3)
• Any exploratory or strategic work that is not on the 14-week execution map

The Samia Problem

Samia is at 30% FE (~12 hours/week) while also managing QF marketing. The plan asks her to:

• Run the landing page A/B test and analyze results
• Manage the 4-email dormant reactivation sequence
• Set up pre-renewal automation
• Launch and scale the organic content engine (3 pieces/day)
• Source and manage graphic designer and video editor contractors
• Test organic content as paid ad creative
• Clean up email segmentation in ActiveCampaign
• Prepare soft launch and full rollout communications
• Begin Ramadan 2027 campaign planning

At 12 hours/week, this is 168 hours over 14 weeks. The organic content engine alone -- even with contractors doing the production -- requires 6-8 hours/week of editorial direction, content selection, posting, and performance analysis. That consumes half her allocation before any ads, emails, or communications work begins.

What breaks first: The organic content cadence. The plan calls for 3 pieces/day by Week 8. With a contracted video editor and graphic designer, Samia's role is editorial direction and posting -- but even that is 1-2 hours/day. At 12 hours/week, the organic engine either takes over her entire allocation or it runs at 1 piece/day instead of 3.

The pressure valve:

1. Reduce the organic content target. 1 quality piece per day is achievable with contractors. 3 pieces/day is a full-time social media manager's job. Hitting 1/day for the first 8 weeks and scaling to 2/day when the production rhythm matures is honest. Promising 3/day and delivering 1/day erratically is worse than promising 1/day and delivering it consistently.

2. Batch the email work into Week 1-4 and then hand ongoing deployment to Sohail/Eshail. After the dormant sequence and pre-renewal automation are set up, Samia should not be touching email execution. She writes the strategy; Sohail/Eshail and Momina execute. This recovers 2-3 hours/week from Week 5 onward.

3. Defer QF marketing to the extent possible during Week 5-10. This is the FE critical path window -- content engine launch, organic content ramp, ad creative testing. If QF marketing can coast on existing campaigns for 6 weeks, Samia gets the hours she needs. This requires Kamran to negotiate with whoever owns QF targets.

What Samia should stop doing, explicitly:

• Manually scheduling or deploying emails (hand to Sohail/Eshail)
• Designing social content herself (hand to contracted graphic designer and video editor)
• Any QF campaign launches during Weeks 5-10 that are not already committed

The Shared Resource Crunch

Momina, Wasif, Sohail/Eshail, and eventually the graphic designer are all shared across multiple products. No one has formal FE hours allocated. This means every request is a negotiation, every deadline is soft, and every other product's urgent need can preempt FE work.

Recommendation: In Week 1, Kamran formally requests from Noor a Q2 priority designation for FE across shared resources. Not exclusive access -- that is unrealistic. A statement: "When FE requests conflict with non-urgent requests from other products, FE takes priority during Q2." This costs nothing but gives Kamran standing to make the call when Momina has competing deadlines.

5. The Decision Calendar

These are not milestones. These are moments when a human being must look at information and make a call. Each one has a named decider, the information required, and the consequence of delay.

The Two Decisions That Cannot Slip

1. CPL hire by Week 4. If this slips past Week 4, activate the contingency the same week. Do not "give it another week." The content timeline has zero slack.

2. Phase 1 checkpoint at Week 6. This is not a status update. It is a go/no-go for the Week 10 soft launch. If engineering is behind, if the CPL has not produced enough frames, if acquisition is not generating data -- the team must decide whether to push the soft launch to Week 12-13 or descope. Hiding behind "we are working on it" at Week 6 guarantees a crisis at Week 10.

6. The CEO Touchpoints

Noor runs a $5M organization. He does not have time to manage FE's weekly operations, and the Operating Agreement correctly places him in a bi-weekly/monthly cadence. But the strategy calls for decisions that only Noor can make or accelerate, and those moments must be designed.

The Cadence

What Noor Should Not Be Asked to Do

• Attend weekly team syncs
• Review individual contractor decisions or small budget items (under $2,000)
• Provide input on content selection, social media strategy, or technical architecture
• Arbitrate between Kamran and Samia on operational trade-offs (Kamran's job as Ameer)

What Noor Must Do That No One Else Can

• Activate his network for the CPL hire. This is a 2-hour investment that could save the entire Q2 timeline.
• Approve the Q2 priority designation so Kamran has standing to pull shared resources.
• Attend the Week 6 deep dive. If Noor skips this meeting, the team will not have the authority to make the go/no-go call on soft launch, and the plan will drift.
• Make the Phase 1 gate decision at Week 14. Continue investing, scale back, or pivot. Only the CEO can commit the organization's resources for Q3-Q4.

The Format That Works

Every written update from Kamran to Noor should follow this structure, no exceptions:

FAITH ESSENTIALS — WEEK [X] UPDATE

SCORECARD
- Active subscribers: [number] (target: [number])
- MRR: $[number] (target: $[number])
- CPA: $[number] (target: ≤$25)
- New subscribers this period: [number]

STATUS: [ON TRACK / AT RISK / OFF TRACK]

THIS PERIOD
- [Accomplishment 1]
- [Accomplishment 2]

NEXT PERIOD
- [Priority 1]
- [Priority 2]

DECISION NEEDED (if any)
- [Decision description] — need your input by [date]

One page. No attachments unless Noor asks. The scorecard numbers tell the story. The status line forces Kamran to make a judgment call every two weeks. The "decision needed" section is how Noor knows whether he needs to act or just acknowledge.

7. What This Plan Honestly Cannot Do

Honesty requires acknowledging the gaps.

The plan cannot produce 3 pieces of organic content per day by Week 8. Not with Samia at 30%. Realistic target: 1 piece/day by Week 6, scaling to 2/day by Week 10 if contractors are reliable. Adjust expectations accordingly, and do not measure Samia against a cadence that requires a full-time social media manager.

The plan cannot implement 3-tier pricing ($9/$15/$30) during the 90-day window. The engineering work alone -- new Stripe products, checkout flow changes, tier gating in the app, marketing page updates -- is 30-50 hours. Kamran does not have those hours while building the daily reflection feature. Recommendation: launch with the existing $15/month and $120/year pricing. Add the $9 tier in Q3 after the daily practice is validated. Add the $30 Supporter tier in Q4 with the Ramadan campaign.

The plan cannot guarantee the CPL hire. The role requires a rare combination of Islamic scholarship, editorial instinct, and production management. The talent pool is small. If the hire fails entirely, the daily practice launches in Q3 at the earliest, and Q2 becomes an acquisition-only quarter. That is not catastrophic -- the dormant reactivation, ad optimization, and email automation can still generate significant value -- but it means the transformative product vision waits.

The plan cannot protect Kamran from organizational pull. At 40% FE, he is one QF crisis away from losing a week of build time. The pressure valves described above (delegate QF oversight, stop IT triage) require organizational buy-in that may not materialize. If Kamran's actual FE allocation drops to 25-30% due to other demands, the engineering timeline extends by 3-4 weeks and the soft launch moves to Week 13-14.

The plan works if three things hold: the CPL is hired by Week 5, Kamran maintains 16 hours/week on FE, and the contractors deliver on time. Remove any one of those and the timeline shifts by a month. Remove two and you are replanning from scratch.

The strategy is genuinely beautiful. The question is no longer the strategy. The question is whether this organization will protect the 0.7 FTE and the $82,000 from the gravitational pull of everything else AlMaghrib does. That is not an execution question. It is a leadership question. And it is the one question this document cannot answer.