Block Gemini

Explore the connected ecosystem.

Can one customer order reach two delivery sites?

Follow a portal order into the back office. A routine single-site order fits the current system. A split order exposes the business rule a custom extension would need to own.

Scope my software project

Interactive example · fictional records

Choose an order condition

Customer order SO-26 · Equipment delivery

12
84

Allocation record · North 8 and south 4 approved

Portal order
One purchase reference
Allocation record
North 8 and south 4 approved
Operations queue
Two linked dispatches
Approved allocation
Review decision

Release the two allocations together

An operations reviewer confirms both destinations. Each dispatch carries the same customer order reference, so a retry can find the existing records.

Scope my software project

What we can build with you

A working slice from customer portal to back office, with a clear owner for split allocations and a return path for delivery status.

Bring to discovery
Bring a standard order, a split shipment and the interfaces your current order system supports.
How to test the pilot
Replay one order, one split and one repeated submission. Compare the dispatch quantities and references with the approved order.
Implementation details and questions

Product owners, founders and technology leaders with a workflow that off-the-shelf software cannot fully support.

We design and build web applications, mobile experiences, customer portals and enterprise platforms around your workflows. Strategy, UX, frontend, backend, quality and deployment move together.

  • Customer portals and self-service journeys
  • New SaaS products and operational applications
  • Modernising a critical legacy workflow
  1. Shape the product

    Map the users, core tasks and commercial assumptions. Prototype the highest-risk journey before committing to the complete system.

    A testable product brief and prototype
  2. Engineer the working system

    Build interfaces, APIs, data models and roles in reviewable increments. Add AI only where its output can be tested against the task.

    Working features with agreed acceptance checks
  3. Release and hand over

    Test integrations, prepare migration and rehearse recovery. Agree documentation, ownership and ongoing responsibilities before launch.

    A release package and operating plan

Interface → application services → data and identity → integrations. Tenant isolation, permissions and migration are designed around the product, rather than added after launch.

  • Discovery, product strategy and UX design
  • Web, mobile, portals and multi-tenant SaaS
  • APIs, databases, identity, roles and admin tools
  • Modernisation, release engineering and ongoing delivery

Use a product where it fits. Build the differentiating workflow, interface or business model around your own requirements.

  • Scope, timeline, ownership and support are agreed for the engagement. A prototype is not a production release.
  • Integration feasibility depends on the source systems, APIs, permissions and data quality.

Bring to discovery

  • Users, business goals and a priority workflow
  • Existing systems and access constraints
  • Data, deployment and ownership requirements
Can you work with our existing engineering team?

Yes. The delivery plan can cover a dedicated build or a scoped workstream embedded with your team, with responsibilities and handover agreed together.

Do we need a complete specification first?

Start with the problem, users and existing process. Discovery can turn those inputs into a prioritised scope and first acceptance milestone.