Primary Offer · Limited Availability
Fix Your Biggest iOS or AI Bottleneck in 6 Weeks
Without hiring a full-time principal or rewriting everything
Your build takes 15 minutes, your AI feature burns €2,000 per month, or a critical launch is at risk. You do not need another 50-page audit—you need a design authority who helps your team ship the right fix and documents the path forward.
Format: 6 weeks · 10 hours/week of Design Authority
Investment: €12,000–€18,000 fixed fee
Your team's role: Execute the solution with expert oversight
My role: Architect, review, unblock, and ensure quality
This model works when you already have capable engineers. I design the fix, keep standards high, and make sure the solution sticks. You keep control of the code and the momentum.
"Igor is very experienced, knowledgeable and honest. Will be reaching out for my future needs. Thank you!"
— Aline Tomasian
Common Bottlenecks We Fix in Six Weeks
What we do
- Week 1-2: Map your dependency graph and identify the seams for modular boundaries.
- Week 3-4: Design the target architecture and review your team's extraction work.
- Week 5-6: Validate build improvements, document module ownership, and lock in guardrails.
Recent outcome: Cut build time from 18 minutes to 7 minutes for a 200k LOC codebase.
Your AI feature is unreliable and bleeding money
The LLM integration works in demos, fails in production, and costs are unpredictable because there's no governance.
What we do
- Week 1-2: Audit the implementation, design a prompt library, caching strategy, and observability plan.
- Week 3-4: Install evaluation harnesses, add guardrails, and train the team on governance.
- Week 5-6: Optimize for quality and cost, document the runbook, and align on future iteration cadence.
Recent outcome: Reduced LLM spend from €2k to €40 per month while increasing reliability.
What we do
- Week 1-2: Review the current approach and design a migration strategy that fits your release cadence.
- Week 3-4: Pair through critical PRs, establish repeatable patterns, and coach the team on testing.
- Week 5-6: Validate coverage, document architecture decisions, and hand off a sustainable roadmap.
Recent outcome: Migrated an 80k LOC app to TCA without production incidents or missed milestones.
What we do
- Week 1-2: Deep dive profiling to surface non-obvious bottlenecks across client and backend.
- Week 3-4: Design targeted fixes, review implementation, and set performance budgets.
- Week 5-6: Validate improvements in production-like environments and document ongoing guardrails.
Recent outcome: Reduced launch time from 4.2 seconds to 1.8 seconds on iPhone 12 across the critical flows.
How This Engagement Works
I'm not joining as a full-time contractor. I operate as your design authority so your team learns by doing and ships the solution with confidence. Here's the cadence that keeps us aligned without burning through hours.
Weekly cadence (10 hours/week)
- Monday:
- Review last week's commits and production telemetry.
- Deliver async PR feedback on architectural decisions.
- Tuesday–Wednesday:
- Deep work on the next architecture spike or design doc.
- Document patterns and decision rationale your team can implement immediately.
- Thursday:
- 90-minute live session to unblock, pair, and answer questions.
- Adjust implementation plans based on what your team learned that week.
- Friday:
- Final PR reviews before the weekend.
- Written update covering progress, blockers cleared, and the next week's focus.
What your team does
- Have 1-2 engineers available to implement the plan during the six weeks.
- Commit code daily so feedback lands while context is fresh.
- Join the weekly live session prepared with questions and decisions that need resolving.
- Own the solution after handoff—my goal is to make your team self-sufficient.
What I do
- Design the target architecture, migration path, or performance fix.
- Review every critical PR with async feedback inside 24 hours on business days.
- Unblock complex decisions during live sessions and ad-hoc pairing.
- Document architecture decisions, runbooks, and next steps so momentum continues after the sprint.
This model works because your engineers stay hands-on, absorb the patterns, and own the result. My job is to prevent €50k mistakes, keep decisions on track, and hand back a system your team can extend.
Before You Book
You're a great fit if
- You have a clearly defined bottleneck that is blocking revenue or delivery.
- Your team has the capacity to execute with guidance and wants to own the code.
- You value architectural clarity over throwing more engineers at the problem.
- You can commit to a six-week window and steady implementation pace.
This won't work if
- You need a full-time contractor to write all the code for you.
- Your team is already over capacity and cannot implement recommendations.
- You're looking for a broad audit without fixing anything.
- You need a solution in under two weeks—book Sessions instead.
Investment & Timeline
The sprint is a fixed fee between €12,000 and €18,000. Pricing is locked before kickoff and tied to the scope we agree on together.
What influences pricing
- Problem scope: tackling one bottleneck versus a system-wide issue.
- Integration surface area: iOS-only or iOS plus backend and infrastructure.
- Team readiness: whether discovery is complete or we must validate root causes first.
Timeline you can expect
- Discovery call this week to confirm fit and goals.
- Fixed proposal and scope within 48 hours of the call.
- Kickoff within two weeks, aligned with your team's release cadence.
- Six weeks of focused work with weekly live touchpoints.
- Handoff and 30-day follow-up support to ensure adoption sticks.
What's included
- 60 hours of Design Authority time across six weeks (10 hours per week).
- Daily async PR reviews and Slack guidance during business days.
- Weekly 90-minute live architecture session with your team.
- Architecture decision records, diagrams, benchmarks, and handoff materials.
- 30-day follow-up in Slack after handoff for clarifications.
Not included
- Full-time implementation—your engineers execute the plan.
- Ongoing support beyond the 30-day follow-up (see Retainer).
- Emergency weekend or overnight work (Sessions cover urgent needs).
Frequently Asked Questions
Why does this take six weeks if you only work 10 hours per week?
Your team needs time between touchpoints to ship code while the context is fresh. Six weeks gives us room to design, implement, validate, and document without burning out your engineers. If I joined full-time for two weeks, you'd get code you didn't help build. This model ensures your team owns the solution and keeps momentum after I'm gone.
Can't you just work full-time for a shorter period?
I intentionally keep a full-time role so my advice is grounded in current production realities. My consulting capacity is capped at 10 hours per week, which I reserve for design authority work. If you need full-time implementation, I can introduce trusted contractors while I stay involved for architecture oversight.
How much time does this require from my team?
Plan on one to two engineers dedicating meaningful time each week. They will implement the architecture, attend the 90-minute session, and act on daily review feedback. If your team cannot commit this time, the sprint will stall—consider booking targeted Sessions instead until you free capacity.
What if the problem turns out to be bigger than six weeks?
We focus on the highest-leverage slice. If we uncover more work, we can scope a follow-up sprint, transition to the monthly Retainer, or hand off a roadmap your team executes. Most teams ship the critical fix inside the initial six-week window and continue independently.
Do you write code or only review?
Both. Expect me to draft architecture spikes, example implementations, and pair on tricky parts. Your team still writes most of the production code so they fully understand it. Think 80% design and review, 20% hands-on pairing where it matters most.
What if we already ran an audit?
Great—bring the findings. We'll choose the highest-impact recommendation and execute it together so the audit stops collecting dust. Many teams have outstanding reports with no plan to implement; this sprint converts the plan into shipped improvements.
Can we extend beyond six weeks?
Yes. If you want continued oversight, we can scope another sprint or move into the €1,600/month Retainer. Some teams alternate: sprint to tackle a major blocker, retainer to maintain momentum.
Ready to Fix Your Bottleneck?
Book a discovery call to outline the problem, confirm the sprint timeline, and receive a fixed proposal within 48 hours.
- Discovery call to align on the problem, team capacity, and success criteria.
- Receive a written proposal with scope, fee, and timeline within 48 hours.
- Kicks off within two weeks with discovery sessions, code access, and clear next steps.
Exploring other ways to collaborate? See all consulting services →