Technical Services

Flarewing offers three connected services - consultancy, design, and development - built around getting to the right problem before jumping to a solution.

What Flarewing does

  • Technical consultancy

    Before recommending anything, we work to understand what's actually going on - low donations, poor online visibility, inefficient internal tooling, outdated systems. The right fix depends on getting that diagnosis right first, not on which service sounds most impressive to sell.

    In practice this usually means whiteboarding to pull in context well beyond the immediate ask, and digging into why you believe the thing you're asking for is the weak point. Sometimes that process ends up pointing at a smaller, cheaper, or entirely different fix than what was originally requested - occasionally one that doesn't involve Flarewing at all. That's fine: the priority is you walking away with a solution that genuinely works, not maximising the scope of work taken on.

  • Design

    Web layout and UX/UI design for whatever gets built - making sure the end product is clear, usable, and accessible for the people it's meant to serve. This covers working a logo, colour scheme, and imagery into the site itself.

    Print materials and more involved graphic design work, such as full brand identity development and print collateral, sit outside this scope and are deferred to trusted external designers Flarewing works closely with throughout the project, rather than handed off as a separate, disconnected piece of work.

  • Development

    Building the product itself - websites, web apps, and internal tools - using modern, maintainable technologies suited to what the client actually needs and the systems they're already running.

What's out of scope

  • App development (native mobile apps)
  • General software development unrelated to the web
  • Print materials and more involved graphic design/branding work

Native app development specifically is on hold rather than ruled out for good - it's currently tied to a couple of locked-down platform ecosystems, which isn't a great fit for how Flarewing likes to work. That's worth revisiting if the landscape opens up with more options down the line.

How Flarewing works with you

You work directly with the person doing the actual work, from the first conversation through to launch and support - no hand-offs between account management and delivery, and full attention on your project rather than several at once.

  1. 1

    Discovery

    A free, no-obligation conversation to understand your situation and where Flarewing might help. If it needs to go further (whiteboarding solutions, auditing existing systems, stakeholder interviews), that becomes its own separate step, agreed with you before it starts. See Pricing Approach below for how that's costed.

  2. 2

    Scoping

    Once the real problem is clear, it becomes a concrete plan - a feature list broken into logical sets, the technology choices suited to your needs (including whether to build on an existing setup or start fresh), a timeline, and cost. That plan becomes the agreed proposal, and nothing starts until you've signed off on it and know what you're paying for.

  3. 3

    Build

    Design and development happen with regular check-ins, not as a black box that reappears at the end. You're working with the same person throughout, and accessibility and performance are treated as part of the build itself. Anything genuinely new that comes up gets logged and talked through rather than quietly expanding the project.

  4. 4

    Handover & ongoing care

    At launch, you get what you need to run things day to day - documentation and training on how everything works, plus hands-on access to make changes yourself where that's appropriate for what's been built. Flarewing also keeps a standing eye on uptime, SSL certificate status, and domain expiry after launch. There's no retainer to sign up for - further work is simply priced and handled as and when you need it.

Pricing approach

Charities and mission-led teams are already stretched thin day to day - pricing shouldn't be one more thing to untangle. That's why it's built on transparency and simplicity: a clear cost upfront, in plain language, and never more than the work actually needs. No project is too small to be worth a conversation: work ranges from a single feature addition to a full platform build, covered in the breakdown below.

There's no ongoing retainer or subscription to sign up for. Work is scoped and priced per project, and anything needed after launch, whether a fix, a tweak, or a new feature, is billed the same way, as and when it comes up.

Work types

  • Technical consultancy

    A standalone diagnostic when what's needed is clarity, not necessarily a build - whiteboarding to get to the root of the problem, auditing existing systems, several stakeholder interviews, or a written recommendation. Kicks in once a conversation moves from discussing the problem to actively solving it - charged as a modest flat fee, credited against a project if one follows.

  • Simple site or small feature

    A straightforward website, landing page, or a single scoped feature added to something that already exists. Usually the shortest kind of project, priced as one fixed quote and paid in two stages - a deposit to start, the balance at launch.

  • Custom build

    A multi-feature web app or platform - several connected pieces working together, often combining design, development, and subcontracted specialists. Scoped upfront as a fixed quote, then paid in stages as each working milestone is delivered, rather than all at once.

  • Ongoing or open-ended work

    Work where scope keeps evolving rather than settling into a fixed brief - additions to an existing project, or a short exploratory piece without a clear endpoint yet. Billed at a day rate instead, agreed before work starts and tracked as it happens.

What affects cost

  • The size and complexity of what's being built
  • Whether existing systems need auditing or integrating with
  • Whether subcontracted design work is needed - kept as its own line item in any quote, so it's always clear what's paying for what
  • Whether there's a genuine budget constraint to work around

Budget constraints are a normal part of working with charities, nonprofits, and other mission-led organisations, and that's understood going in. Where a real constraint exists, each case is reviewed individually to see what can be done to help.