Neptune Digital

Trusted by clients from global brands to local charities

One division, one urgent problem, and a procurement process built for something bigger.

The need is real and the deadline is fixed. The usual suppliers move at the pace of the whole organisation.

  • We need it working before the event, not after the next budget cycle.

  • Our big suppliers want six months to scope a change.

  • IT, security and procurement all need to sign it off.

  • We have to show the board what it returned.

Everyone who has to say yes, on one map

Enterprise work has many stakeholders. We map them at the start, give each the evidence they need, and keep the work moving between them.

  1. 1
    Your champion

    Names the problem and the deadline

  2. 2
    Our team

    Workshop and a clickable prototype

  3. 3
    IT and security

    Reviews the stack and access rules

  4. 4
    Procurement

    Agrees terms and a range

  5. 5
    Our team

    First release in use

  6. 6
    Your champion

    Shows the return to the board

How we built it

Systems built beside the teams that run on them

Three builds, each told the way the client would, with what stood in the way and what we built.

  1. PolicyHub: an equine policy with its schedule of horses, one horse open with its coverages

    Bascule Underwriting · Customer portals

    Agents and underwriters work every policy, horse and claim in one place

    The challenge

    An equine policy is a schedule of horses, each with its own value, cover and history; a farm policy is locations and liabilities. That detail lived in FileMaker layouts, claim boards, online forms and a helpdesk, so agents relied on Bascule's team for it, and the team moved between tools to find it.

    What we built

    We built PolicyHub as the one place both work. Agents see their book, quote and follow claims; Bascule's team underwrites, handles claims and runs commission. It reads policies, horses and invoices live from FileMaker, so nothing is copied and the business never had to stop.

    Next.jsSupabaseFileMakerClaudePostHogVercelRead the case study
  2. A hotel booking on Travel Places' operations platform, its process running from confirmed to closed

    Travel Places · Business systems

    One platform for every event, booking and supplier

    The challenge

    A team's trip touches every part of Travel Places, from the agent who books the hotel and the operations team who sees the squad through the airport to the accounts team who invoices it and claims the commission afterwards. For years each department kept its own view of that trip, in FileMaker layouts and spreadsheets, and passed it on.

    What we built

    We built one platform on the web that every department works from. An event holds its clients, bookings and suppliers; a booking carries its rooms, rates, payments and commission from confirmation to close, and moves itself on at each step. FileMaker stays in step underneath, so nothing had to stop for the switch.

    Next.jsSupabaseFileMakern8nPostHogVercelRead the case study
  3. A dense, grey booking screen beside the same booking on the web

    Fliteline · Migration

    A 14-year-old FileMaker system moving to the web, one module at a time

    The challenge

    Everything Fliteline does runs through one FileMaker system, built up over about 14 years. It works, and it is dense. And like many FileMaker systems, it depends on finding developers who know the platform and the business behind it, and it is hard to open up to customers and other tools.

    What we built

    We took the system on rather than replacing it, and kept improving it while the business ran on it. With what that taught us, Fliteline's team and ours are rebuilding it for the web one module at a time. Each is designed as a clickable prototype, signed off by the people who will use it, then built, with the whole system moving across in one cut-over.

    FileMakerNext.jsSupabasen8nVercelRead the case study

What your IT and procurement teams get

The answers they need, early, so sign-off doesn't hold up delivery.

  • The stack, hosting region and access rules, written down
  • Platforms independently audited every year (Vercel and Supabase)
  • Our policies and security posture in the trust centre
  • Estimates as ranges, with priorities agreed a month at a time

What clients say about working with us

  • Extremely satisfied. The team are extremely responsive, flexible, fast, and precise in all areas. We started together with a small project, and have since expanded the SoW significantly after the service and talent we got. 10/10, would recommend.

    William HillCEO, Bascule Insurance Services LLC
  • Working with Neptune has been an exceptional experience from start to finish. Their dedication, expertise, and swift execution in developing our system left me thoroughly impressed. The seamless communication and willingness to go the extra mile demonstrated their commitment to delivering excellence. Overall, my experience with Neptune has been nothing short of outstanding.

    Jacquie FreearPurchasing Manager
  • Neptune is highly creative, diligent in research, and provides excellent suggestions. We have accomplished much and thoroughly enjoyed our real-time suggest-and-edit sessions. Neptunes' flexibility and adaptability have resulted in impressive productivity within tight time frames and with exceptional quality.

    Craig CameronHead of R&D
  • I highly recommend working with Neptune. The process is hugely collaborative and made the project a joy to work on. Their understanding of FileMaker is second to none and they always finds ways to solve challenges through creative design. They are organised, calm and diligent in their work, and will go above and beyond to deliver.

    Mark HoldenManaging Director
  • Neptune provided an excellent professional, knowledgeable service and offer exceptional value to any project. Thank you to Jordan and the Team.

    Darren WilliamsProduct Owner, Solotech

Questions from enterprise teams

  • Early. Your IT team gets the stack, hosting region and access rules in writing; the platforms we build on are independently audited every year; our policies are in the trust centre.

    Trust centre
  • Yes. The code and the data are yours. The code lives in a repository you can hold, the data comes out with standard tools, and another supplier could pick it up.

  • Yes. We connect to the systems and suppliers you already have, and build the part they can't.