FFancy Bouw.
FB / Services — 13 disciplines

What we build,
how we build it.

Thirteen service lines that combine into complete engagements. Each one includes what the work covers, the business problem it solves, how we typically deliver it, and the practices and technologies involved.

Abstract wireframe of a cloud network with luminous connection points
  1. § 01

    Custom Software Development

    What it includes
    Full-cycle development of bespoke applications: requirements analysis, architecture, implementation, testing, and release.
    Problems it solves
    Fits problems that off-the-shelf products cannot cover — internal tools, specialized workflows, or products with unique domain logic.
    Delivery approach
    Small senior teams, short iterations with running software each cycle, and written architecture decisions kept alongside the code.
    Technologies & practices
    TypeScript, Python, Go, Rust, PostgreSQL, REST/GraphQL APIs.
  2. § 02

    Web Application Development

    What it includes
    Modern web applications with typed frontends, server-rendered pages where appropriate, and accessible user interfaces.
    Problems it solves
    Customer portals, dashboards, internal tools, and product web apps that need to remain fast and maintainable as they grow.
    Delivery approach
    Component-driven design, static typing throughout, performance budgets set from day one, and testing across unit and end-to-end levels.
    Technologies & practices
    React, Next.js, TanStack, Node.js, TypeScript, Playwright.
  3. § 03

    Mobile Application Development

    What it includes
    Native and cross-platform mobile applications for iOS and Android, from prototype through store release and ongoing updates.
    Problems it solves
    Consumer-facing apps, field tools, and mobile companions to existing web platforms that need to feel native on device.
    Delivery approach
    Shared codebase where it makes sense, native modules where it does not. Explicit offline, background, and battery behavior.
    Technologies & practices
    React Native, Swift, Kotlin, Expo, native modules where required.
  4. § 04

    UI and UX Engineering

    What it includes
    Interaction design and implementation, design systems, accessibility work, and the boundary layer between design and engineering.
    Problems it solves
    Products that feel inconsistent across screens, teams that struggle to keep design and code in sync, or accessibility gaps in existing UIs.
    Delivery approach
    Design tokens and component libraries defined once and reused everywhere; accessibility is treated as a baseline requirement.
    Technologies & practices
    Tailwind, Radix, WCAG 2.2, semantic HTML, TypeScript component libraries.
  5. § 05

    Cloud Solutions

    What it includes
    Cloud architecture, migration, and workload design across AWS, Google Cloud, and Azure. Infrastructure as code from the first environment.
    Problems it solves
    Rising infrastructure cost, unreliable environments, or the need to move workloads out of legacy hosting into modern cloud services.
    Delivery approach
    Small blast radius by default: separate accounts or projects per environment, least-privilege IAM, and clear cost boundaries.
    Technologies & practices
    AWS, GCP, Azure, Terraform, Pulumi, Kubernetes, container services.
  6. § 06

    DevOps and Infrastructure

    What it includes
    Delivery pipelines, environment automation, container orchestration, observability, and on-call practices.
    Problems it solves
    Slow, manual releases, brittle environments, and gaps between the code that runs in development and the code that runs in production.
    Delivery approach
    Everything through pull requests: infrastructure, pipelines, and policies. Observability configured before features go live.
    Technologies & practices
    Kubernetes, Docker, Terraform, GitHub Actions, GitLab CI, Prometheus, OpenTelemetry.
  7. § 07

    API Development and Integrations

    What it includes
    Design and implementation of internal and public APIs, plus integrations between SaaS products, internal systems, and third-party services.
    Problems it solves
    Systems that cannot talk to each other, brittle point-to-point integrations, or missing developer experience around existing APIs.
    Delivery approach
    Contract-first with OpenAPI or GraphQL schemas, versioning discipline, and strong test coverage of integration edges.
    Technologies & practices
    REST, GraphQL, gRPC, OpenAPI, Kafka, webhook infrastructure.
  8. § 08

    Data Engineering

    What it includes
    Data pipelines, warehouses, event streaming, and the operational tooling around them. From ingest through modeling to reporting surfaces.
    Problems it solves
    Reports that no one trusts, dashboards built on ad-hoc queries, or product features that need reliable event data.
    Delivery approach
    Explicit contracts between producers and consumers, versioned schemas, and data quality tests treated like any other test suite.
    Technologies & practices
    PostgreSQL, BigQuery, Snowflake, dbt, Kafka, Airflow, event schemas.
  9. § 09

    Cybersecurity Consulting

    What it includes
    Threat modeling, secure code review, penetration-test remediation, and hardening of application and infrastructure configuration.
    Problems it solves
    Findings from an external audit, new regulatory obligations, or a general lack of confidence in how sensitive data is handled.
    Delivery approach
    Practical work integrated into the development process rather than a one-off report. Every finding ties to a concrete change in the system.
    Technologies & practices
    STRIDE, OWASP ASVS, SAST/DAST tooling, secret management, IAM hardening.
  10. § 10

    Software Modernization

    What it includes
    Structured modernization of legacy applications: language migrations, monolith decomposition, framework upgrades, and platform re-hosting.
    Problems it solves
    Systems that still work but are slow to change, expensive to run, or difficult to hire for. The goal is to keep behavior while improving foundations.
    Delivery approach
    Strangler-style, testable, reversible steps. Never rewrite in one big jump; every change ships and can be rolled back.
    Technologies & practices
    Refactoring toolchains, characterization tests, strangler patterns, contract tests.
  11. § 11

    Technical Consulting

    What it includes
    Architecture reviews, technology selection, due diligence, and hands-on advisory for engineering leadership.
    Problems it solves
    Decisions where the cost of getting it wrong is high — platform choices, buy-versus-build, hiring strategy, or investment-driven due diligence.
    Delivery approach
    Short, focused engagements that end in a written recommendation backed by evidence, options, and trade-offs, not just an opinion.
    Technologies & practices
    Architecture assessments, ADRs, roadmap reviews, technical due diligence.
  12. § 12

    Quality Assurance and Testing

    What it includes
    Test strategy, automated test suites, performance and load testing, and quality gates in delivery pipelines.
    Problems it solves
    Slow release cycles caused by fragile manual testing, or products where regressions keep reaching users.
    Delivery approach
    The test pyramid taken seriously: many fast unit tests, focused integration tests, and a small, reliable end-to-end suite.
    Technologies & practices
    Vitest, Jest, Playwright, Cypress, k6, Locust, contract testing.
  13. § 13

    Maintenance and Technical Support

    What it includes
    Ongoing support for systems in production: bug fixes, security updates, dependency upgrades, and small feature work.
    Problems it solves
    Software that no longer has a dedicated team and needs a reliable, accountable partner to keep it healthy over time.
    Delivery approach
    Fixed monthly capacity with clear service levels, transparent reporting, and a documented handover the day the engagement ends.
    Technologies & practices
    Structured incident response, dependency governance, monitoring, runbooks.