Consulting

Engagements I take on, and how to start one.

Five engagement shapes I work in, and one process that fits all of them. The fastest way to find out if I’m a fit is to email me.

Engagement models

Five shapes I work in.

Pick the one closest to your situation. The proposal will adjust the details to fit.

  • Architecture audit

    1–2 weeks

    A short, focused review of an existing codebase, system, or migration plan. You get a written report and two or three working sessions.

    Pricing
    Fixed scope
    Best for
    Pre-investment due diligence, post-incident reviews, validating a scaling plan.
  • Greenfield MVP build

    6–12 weeks

    Building a new product from architecture to launch. Best when the scope is clear and the stack is Django and Next.js or close to it.

    Pricing
    Fixed scope or T&M
    Best for
    Founders shipping a v1, internal tools, customer-facing SaaS.
  • Fractional development

    Ongoing

    10–25 hours per week, async-first, embedded with your team. Best for long engagements where deep context pays off.

    Pricing
    Monthly retainer
    Best for
    Small teams that need a senior engineer without a full FTE hire.
  • Performance & scaling

    2–6 weeks

    Profile, find the real bottleneck, fix it, and document the playbook so the team can repeat it. Usually Django performance work, but applies broadly.

    Pricing
    Fixed scope
    Best for
    Teams whose product is slow, expensive, or both.
  • Advisory only

    Per call

    One-off architecture conversations, technology selection, hiring help, code review. No commitment beyond the call itself.

    Pricing
    Hourly
    Best for
    Quick second opinions, early-stage decisions.
Process

From email to kickoff in roughly a week.

No sales funnel, no scoping calls disguised as discovery. The shortest honest path to a yes or no.

  1. 01

    Email with context

    Send a short brief: target stack, scope, timeline, budget bracket. I respond within 1–2 business days with availability and questions.

  2. 02

    Discovery call

    30–45 minutes. We walk through the problem, the constraints, and decide whether we're a fit. Not a sales call.

  3. 03

    Proposal

    Written scope, milestones, pricing, and what success looks like. Usually 24–48 hours after the discovery call.

  4. 04

    Kickoff

    Once approved, we ship. Async-first, weekly sync, decisions in writing.

Frequently asked

Things people email about.

What stacks are you most useful in?+

Django and FastAPI on the backend; Next.js, React, and React Native on the frontend; PostgreSQL and Redis on data. SaaS products, API platforms, and developer tooling are sweet spots.

What time zones do you work in?+

Async-first across all timezones. Live calls flex to your team's hours within reason.

Do you take on small projects?+

Yes, including audits, advisory calls, and fixed-scope improvements. Don't assume the project is too small to email about.

Do you sign NDAs?+

Yes, when the engagement warrants. For early conversations a mutual NDA is fine; standard business terms apply.

What's your rate?+

It depends on scope, duration, and engagement model. Email shkeiryasser@gmail.com with project context for a quote.

Are you a generalist or a specialist?+

Specialist on Django + Next.js fullstack work; generalist enough to handle adjacent stacks. If your project is far outside the Python/JavaScript ecosystem, I'll tell you upfront.

Ready when you are.

Email shkeiryasser@gmail.com with scope, stack, timeline, and budget bracket. Response within 1–2 business days.