Skip to main content
How We Work

No surprises. No handoffs. Every phase has a clear owner and a clear output.

This is how a Fordel engagement actually works — from first conversation to 30 days post-launch. Read it before we talk. It will save us both time.

01

Scoping Call

30 minutes

You describe what you need. I tell you whether it is feasible, what it would realistically take, and whether Fordel is the right fit. No deck, no pitch, no pre-call questionnaire. Just a direct conversation.

  • Understand your actual problem, not the feature list
  • Identify the real complexity — where estimates usually break
  • Tell you clearly if something is outside our scope
02

Architecture

1–3 days

Before a single line of production code is written, we map the system. What gets built, what integrates with what, where the risk lives. You get a written architecture document you own regardless of whether we proceed.

  • System design with explicit tradeoffs
  • Integration map — third parties, existing systems, data flows
  • Risk register: what could go wrong and how we prevent it
03

Build

Project-dependent

AI-accelerated development with human oversight at every step. Working software ships weekly — you see real progress, not status updates. Scope changes are flagged before work starts, not after.

  • Weekly working software, not just updates
  • Scope change protocol: flagged and agreed before work begins
  • Async-first communication — you hear about blockers immediately
04

Launch

1–2 days

Production deployment with monitoring, error tracking, and CI/CD in place before go-live. Launch day should be boring. If it is exciting, something went wrong in planning.

  • Production-grade deployment pipeline
  • Error monitoring and alerting configured
  • Runbook handed off — you know how to operate what we built
05

Post-Launch Support

30 days

Your launch is the beginning of our accountability, not the end. The 30 days after go-live are the ones that matter most — traffic spikes, edge cases, integration failures. We stay on.

  • Active monitoring for the first 30 days
  • Bug fixes included — no change order for launch-window issues
  • Handoff documentation written for your team
Engagement Types
Project

Fixed scope, milestone-based delivery. Suitable for greenfield builds, major feature work, or system overhauls. Architecture document produced before build starts.

Retainer

Ongoing engineering capacity — architecture reviews, feature development, technical support. Fordel integrates with your existing team and process.

Advisory

Technical strategy, AI readiness assessment, architecture review. No code produced. Suitable for teams that need an outside senior perspective before committing to a direction.

What We Don't Do
  • 01Hand off your project to a junior after the pitch
  • 02Write a 40-page proposal before understanding your actual problem
  • 03Disappear after launch and invoice for every subsequent question
  • 04Pretend AI can solve problems where it cannot
  • 05Inflate timelines to buffer for poor planning
  • 06Run multiple projects simultaneously with degraded attention on each

Ready to start?

The scoping call is free, 30 minutes, and no obligation. You describe what you need — I tell you whether we can help and what it would take.

Book a Scoping Call