Skip to content

Software and infra.One team.

Understand your business. Design, build and care for your system — from the first brief to daily use.

01 / 09

One team, the whole system

Consult · Software · Infrastructure · Care

An isometric engineering drawing of the systems CRAFT builds, from web, mobile and desktop apps and the business workflow to APIs, software, cloud and infrastructure. A request from a user passes through every layer and returns as a result, with CRAFT responsible for the whole system.

Built around the work.

From customer-facing screens to the data and infrastructure behind them. Commission a specific part or plan how the pieces work together.

  1. 01

    Web development

    Start with the people using the product, then design around its data, workload, and the team maintaining it. From content-driven websites to internal business applications.

    • Discovery and interface design
    • Websites and web applications
    • Administration and user permissions
    • Databases and API integration
    • Performance, search, and accessibility
    • Deployment and data migration
    Read the scope, process, and deliverables
    Read the scope
  2. 02

    Mobile applications

    Make the small screen work harder. Use React Native for shared application code or Swift for direct access to platform capabilities, with clear tradeoffs from the start.

    • Design for small-screen tasks
    • React Native for iOS and Android
    • Swift for iOS-specific work
    • Accounts, APIs, and notifications
    • Unreliable networks and device access
    • Device testing and release preparation
    Read the scope, process, and deliverables
    Read the scope
  3. 03

    Cloud infrastructure

    Build infrastructure around the actual workload. Separate environments, make changes traceable, and prepare recovery procedures before they are needed.

    • System assessment and architecture
    • Environments and application packaging
    • Infrastructure as code and access control
    • CI/CD and controlled releases
    • Monitoring and incident handling
    • Backup, recovery, and cost control
    Read the scope, process, and deliverables
    Read the scope

Product Design & Interface Systems

Map the work, test the screens, and document what developers need.

  • User tasks and constraints
  • Information structure and journeys
  • Wireframes and prototypes
Explore the scope

Backend Systems, Databases & APIs

Clear data boundaries, access rules, and system integrations.

  • Data models and business rules
  • API contracts and validation
  • Identity and access control
Explore the scope

Maintenance & System Improvement

Understand the existing system. Prioritize fixes. Make changes traceable.

  • System review and technical debt
  • Failure diagnosis and correction
  • Dependency and runtime updates
Explore the scope
Explore all 6 services

Software for the work your business does

Start with the tasks, the data, and the systems already in place. Then decide what belongs on the web, a phone, or a desktop. These are examples of the work we take on, not a limit on the scope we consider.

Systems and technologies

Websites and web applications

  • Astro
  • Next.js
  • WordPress

Company sites and published content can use static or prebuilt pages. Member areas, bookings, and commerce need a backend to manage data, permissions, and transactions. We choose rendering and caching per route, and design publishing tools around the people who maintain the content.

  • Company websites, product catalogs, and publications
  • Member areas, bookings, orders, and customer portals
  • Administration, reporting, and approval workflows
Explore web development

Windows, macOS, and Linux applications

  • Windows
  • macOS
  • Linux

Some work needs access to local files, connected devices, or processes outside a browser. We build installed applications, command-line tools, and background services. Operating-system APIs, permissions, and distribution requirements guide the choice between native and cross-platform implementations.

  • File processing, data imports, and document tools
  • Device integration and Windows API applications
  • Internal desktop software with installation and update plans
Explore desktop and operating-system work

Mobile applications for customers and teams

  • React Native
  • Swift
  • Flutter

iOS and Android applications need to account for screen sizes, cameras, notifications, and unreliable connections. We define offline behavior, data synchronization, and access rules before testing on the agreed devices and preparing the release process.

  • Membership, booking, and service-tracking applications
  • Field work, inspection forms, and photo records
  • Mobile access to existing business systems and data
Explore mobile development

APIs and system integration

  • Node.js
  • Python
  • .NET

Connect websites, applications, accounting, inventory, and external services with explicit data formats and access rules. Plan for unavailable endpoints and repeated requests. Automated changes to important records need an audit trail, duplicate checks, and a way to pause or request human review.

  • REST APIs, webhooks, and system-to-system synchronization
  • Approvals, notifications, and scheduled processing
  • Data imports, validation, and AI tool integration
Explore backends and APIs

Start with a new project or an existing system

A full rebuild is not the starting assumption. Choose a scope around the problem that needs attention and the information available today.

Build a new system

For a business with a workflow but no suitable tool, or a product being developed for the first time. Establish what the first release needs to prove before expanding it.

  • Define users and the first release
  • Design screens, data, and architecture
  • Develop, test, and prepare the release

Extend and connect

For software that still serves its users but has manual steps or missing functionality. Understand its constraints and test how changes affect existing behavior.

  • Review code and integration documentation
  • Add functionality, APIs, or data migrations
  • Plan deployment and rollback

Review and maintain

For a system that is slow, unreliable, or difficult to maintain. Reproduce the problems, collect evidence, and order the improvements before agreeing the work.

  • Inspect bottlenecks, dependencies, and deployment
  • Fix issues and test existing workflows
  • Define maintenance tasks and review intervals
Discuss your system

Know what each stage delivers

Each stage produces work you can review and decisions we need to make together. We distinguish defects from added scope and assess the effect on cost and schedule before changing the plan.

Read the process and preparation checklist
  1. Define

    Understand current workflows, users, and constraints. Prioritize what the first release needs and record what remains outside the scope.

    Output: Brief, scope, and acceptance criteria

  2. Design

    Map user journeys, screens, data, and system boundaries. Check important assumptions before committing to details that are expensive to change.

    Output: Screen prototypes and system design

  3. Build

    Develop in reviewable increments, with code review and testing alongside implementation. Make progress and outstanding decisions visible.

    Output: Working software for staged reviews

  4. Verify

    Test workflows, permissions, invalid data, and integrations on the agreed devices. Involve representative users in acceptance testing.

    Output: Test results and acceptance records

  5. Handover

    Prepare the release and transfer code, documentation, and access. Explain how the system is operated and the terms of ongoing support.

    Output: Handover package and operating instructions

Leave the next team able to operate the system

An application file is only part of a handover. The receiving team needs to know how the system runs, what it depends on, and who controls access. We define those deliverables when agreeing the scope.

Read the handover guide
Code and build instructions
Source code under the agreed rights, tool versions, installation and build steps, and the required environment variables. Credentials are transferred separately from code.
Data and integrations
In-scope data structures, migration procedures, and API documentation, with a record of external systems and the owners of their accounts.
Test results and known limits
Evidence against the acceptance criteria, resolved issues, acknowledged limitations, and work agreed for a later stage.
Release and operating instructions
Deployment, access, backup, and recovery procedures within scope, together with external operating costs and ongoing support arrangements.

Deliverables, ownership, acceptance rounds, and post-delivery support are specified in the agreement for each project.

Stack

The right tools for the work.

Explore technologies and capabilities

Prepare for the first conversation

Practical guidance on writing a brief, choosing a platform, and reviewing a handover, so the first conversation has enough detail to make the next decision.

Before we discuss your project

More questions and answers
How do you estimate cost and schedule?

We consider workflows, user roles, integrations, existing data quality, and release criteria. Start with examples of the current work and what needs to change. Once the scope is clear, we set out the cost, delivery stages, and assumptions that affect the schedule.

Can you work with our existing technology?

We consider projects in any language or framework except COBOL, including web, mobile, desktop, and background services. Before agreeing the work, we review versions, dependencies, code rights, and test coverage. The tools on this website are examples, not an exhaustive list.

Will we receive the source code and own the system?

The agreement defines rights in the custom work and the source code, documentation, and accounts to be transferred. Third-party libraries and services retain their own license terms. We also identify external costs that remain after delivery.

Can we start without a requirements document?

Yes. Explain the current work, its users, the problems, and the outcome you need. Screens or documents with unnecessary personal information removed are useful. We can identify what is known, what needs investigation, and an initial scope to estimate.

What happens after launch?

The agreement sets out correction periods, maintenance scope, contact channels, and response arrangements. New features, changes to external services, and major upgrades are assessed against the work and impact involved.