Skip to content

Working together

How I work.

I build multi-tenant B2B SaaS end-to-end in Next.js and TypeScript, with Unreal Engine work where 3D is part of the product. These are the same things I build and run at QOOP for ImmoScout24, Mileway, and Formwerk. One engineer, direct communication, remote with CET overlap.

This page is the honest version of what that looks like: the shapes an engagement usually takes, how the work actually runs, and where I'm the wrong person to call.

Get in touchCommon questions
In production atImmoScout24MilewayFormwerk

Engagements

What the work usually looks like.

Three shapes the work tends to settle into. They're descriptions, not packages. Most projects start as one and borrow from another once we know more.

MVP build

Idea to live product in 4–6 weeks. Fixed scope, fixed price, weekly demos.

  • Architecture decisions documented
  • Production deployment + custom domain
  • Auth, payments, core flow shipping in week 2
  • 30-day post-launch support included

Typically 4–6 weeks

Usually suits Founders pre-seed to seed who need a real product, not a prototype.

Fractional engineering

10–20 hrs/week on retainer. Treat me like an in-house senior: design, build, ship, ops.

  • Weekly sprint planning + demo
  • Code review + architecture guidance
  • Direct ownership of complete features
  • On-call rotation participation (optional)

Typically 3-month minimum, monthly thereafter

Usually suits Seed–Series A startups that need senior engineering without a full-time hire.

Architecture audit + rescue

1–2 weeks diagnosing what's slow, leaky, or fragile. Roadmap to fix it. Optional hands-on fix.

  • Written report with prioritized findings
  • Architecture diagrams + recommended changes
  • Performance + security + scaling assessment
  • Optional hands-on execution of the roadmap

Typically 1–2 weeks

Usually suits Teams whose codebase has outgrown its original architecture, or who inherited tech debt.

Fit

Where I help, and where I don't.

Worth reading before you write. Ruling yourself out here costs you a minute; finding out three weeks in costs a great deal more.

A good fit

  • A web product that needs one engineer to own it end to end: architecture, build, deploy, and the bits nobody wants to look after afterwards.
  • Multi-tenant B2B SaaS in Next.js and TypeScript. It is what I build and run daily at QOOP, so the hard parts are familiar rather than novel.
  • Products where 3D is part of the job: Unreal Engine pipelines, scene tooling, and getting real-time 3D to behave inside a browser.
  • An existing codebase that has outgrown the shape it was designed in, and you want a straight read on what to fix first.
  • Remote work with European overlap, decisions made in writing, and a demo every week instead of a status meeting.

Not a good fit

  • Anything needing on-site presence or relocation. I work remotely, and pretending otherwise helps neither of us.
  • Slotting in as one contributor among many in a large engineering org. That work is real, but a staffing partner will serve you better than I will.
  • Pure design engagements: brand, visual identity, or UI design handed over as artwork. I build interfaces; I do not design them from nothing.
  • One-off fixes measured in hours. The context I need to be useful takes longer to load than the fix takes to make.
  • Work that needs a team from day one, or guaranteed 24/7 coverage. There is one of me, and a single engineer cannot be an on-call rota.

FAQ

Common questions.

The things people usually want to know before we start.

How do you scope a project?
We talk through what you're building and why, then I write the scope down: which flows ship, which are explicitly out, and what lands in which week. For a fixed-scope build that document is the contract. Nothing starts until we both agree it describes the same product. For a retainer it's lighter: the first month's outcomes, agreed in writing before the clock starts.
What happens if the scope changes?
It usually does, and that's fine. It just has to be visible. On a fixed-scope build, anything outside the written scope becomes a change order we agree on before I build it, so the timeline and the price stay honest instead of quietly drifting. On a retainer, you re-steer priorities at the weekly planning session; nothing needs renegotiating.
What do you need from me to start?
A signed NDA if anything is sensitive, repository and infrastructure access for existing systems, and one person who can make product decisions without a committee. After that, roughly an hour a week: the Friday demo, plus async answers when something needs a decision. The less I have to guess, the less I build twice.
Will the time-zone gap make scheduling painful?
I work CET hours daily for QOOP: around 4 hours of live overlap with London, 5+ with Berlin, and 1–2 with US East Coast mornings. Everything else runs async: written updates, design docs, and a demo you can watch when it suits you.
Payments, contracts, IP ownership?
Standard work-for-hire IP assignment: you own the code and the infrastructure outright. Your contract or mine, whichever is less work for you. Fixed-scope projects are invoiced half at signing and half at launch; retainers are invoiced monthly. Wise, Payoneer, direct USD wire, or your AP system if you have one.
Do you sign NDAs?
Yes, before any sensitive detail is shared. I'm the sole engineer on a B2B SaaS used by major German real-estate firms, so discretion is the baseline rather than a favour.
Can you work alongside an existing team?
Yes. Most of my work at QOOP has been solo, but I also review code, write design docs, pair when it helps, and work inside your repo, CI, and ticketing rather than importing my own. Where I'm less useful is as one contributor among many in a large org. See the fit notes above.
What if the work doesn't fit any of these shapes?
Describe it anyway. If I can do it well, we'll shape something that fits. If I can't, I'll say so plainly and point you toward someone better suited. A decline costs you a day; a bad fit costs you a quarter.

Getting in touch

Email is the best way to reach me.

A couple of paragraphs about what you're building and what you're stuck on is plenty to start with. No brief template, no forms. I read everything, and I'll tell you honestly whether I'm the right person for it.

me@nayeemurrahman.com

If a conversation would be easier than writing it down, my calendar is open on cal.com. Either way works.

Contact

Get in touch.

If you're building something and want a hand, write to me. Same if you just want a second opinion on an architecture decision.

me@nayeemurrahman.com

Prefer to talk? Grab 15 minutes in my calendar.

© 2026 Nayeemur Rahman. All rights reserved.

LinkedInEmail