Kurnell

About Kurnell

Kurnell builds web services and systems for clients with the way of working we refined running our own services. We settle requirements and design in writing before development, and release only changes that pass tests and review. After release, we keep running and improving the service and help bring in customers.

Business

  • Our own services

    Services Kurnell plans and operates itself.

    Our first service is SolvePod, a learning service. The standards and tools we refined running it carry over to client projects.

  • Client projects

    We take on clients' web services and systems, from requirements definition through maintenance.

    We handle planning and design, development, infrastructure operations, security operations, and marketing support in one place.

Capabilities

  • Requirements analysis and definition

    We pin down the features to build and the quality conditions to meet in a requirements document.

    We separate functional requirements (what users must be able to do) from non-functional requirements (quality conditions such as speed, security, availability, and accessibility), and write them down with completion criteria.

  • Service planning and design

    Screen flows, data structures, and business rules, written into a specification.

    We decide what to show and in what order, and design the server and data structure.

  • Web service and web app development

    We build screens for phones and desktops together with the server.

    Screens follow one design standard and accessibility standard, and business rules become code and tests. When one task changes several records, a single failure rolls back all of them.

  • Infrastructure setup and operations (DevOps)

    We automate deployment and ship only changes that pass automated checks to production.

    DevOps joins development and operations into one automated flow. Every deployment is logged so you can see what changed and when, and we roll back to the previous version if something goes wrong.

  • Security review and operations (SecOps)

    We set security requirements at design time and keep checking in operation.

    SecOps treats security as an ongoing part of operations. Admin authentication, login attempt limits, and request forgery protection are the baseline, and we store only the personal data we need. Every change goes through a security review.

  • Marketing support

    Around release, we plan how to bring in customers and help prepare for it.

    We help plan acquisition channels, set up inquiry management, and prepare offline events and B2B sales material.

Project delivery process

  1. Requirements definition

    We go over the problem, users, schedule, and constraints, then agree on scope and completion criteria.

    The agreed scope and completion criteria go into a requirements document. Every later decision starts from it.

    DeliverablesRequirements document
  2. Planning and design

    The specification is settled before development starts.

    When something needs to change, we update the document before the code.

    DeliverablesSpecificationDecision records
  3. Development and QA

    We write tests for each rule in the specification and accept only changes that pass tests and review.

    In the QA (quality assurance) stage, every change goes through automated tests, code review by a reviewer other than the author, and checks on real devices. We use AI for review and test writing; people make the final call.

    DeliverablesSource codeVerification reports
  4. Release

    We finish pre-release checks and deploy to production.

    We set rollback points in advance, and set up acquisition channels and inquiry management at this stage too.

    DeliverablesOperations documentsRelease checklist
  5. Maintenance and enhancement

    We keep fixing issues and checking security, and improve features based on usage data.

    Changes after release go through the same design and verification steps as the first release.

    DeliverablesChange logVerification reports

Working principles

  • The specification leads

    Development and verification follow the specification. We do not build features it does not describe.

  • Decision records

    Important decisions are written down with the reasons and the options we rejected, so anyone can later see why.

  • Every defect becomes a test

    A defect found once is kept as a test. If the same problem comes back, it shows up in testing before release.

  • Handover by record

    Every task leaves a record. If the person in charge changes, the work continues from that record.

Contact

We take service build consultations and partnership proposals. We review each request and reply by email.