INTECH

Preparing your experience

INTECHStart a project
Explore INTECH

Code smart, Not Harder

INTECH / EDUCATION

Software for schools
and education teams

From school correspondence and student affairs to tools for the classroom, we help plan the workflow and build software around the people using it.

Discuss your school systemExplore relevant work
The public sign-in screen, school news and booking calendar
DB Sarabun · School correspondence

01 / What we can help with

Start with the work
your team does

Schools have different workflows and responsibilities. We learn how the work happens before defining the screens and system scope.

Correspondence and coordination

From DB Sarabun

Receive, send and circulate documents, track their status, and manage resource bookings around the organisation’s workflow.

Student affairs

From DEEBUK-SA

Attendance, conduct records and reports for homeroom teachers and student-affairs staff.

Classroom tools

From CHEM RANK

Points, activities and displays that teachers use alongside lessons, based on an agreed teaching workflow.

Each system is scoped together. Data migration, integrations and external service costs are identified separately in the proposal.

03 / Process and deliverables

Agree the plan
before development

Define responsibilities, review points and acceptance criteria so your team knows what to expect at each stage.

  1. Understand the workflow

    Meet the users, review forms and steps, and identify constraints in the existing system.

    What we agree together

    A workflow outline, user roles and the problems to address

  2. Design and scope

    Review screens, access permissions, integrations and the work included.

    What we agree together

    Screen designs, scope, deliverables, milestones and acceptance criteria

  3. Build and test together

    Review progress and have designated users try the important workflows before release.

    What we agree together

    The scoped system, test cases and acceptance records

  4. Hand over and plan support

    Transfer agreed files, documentation and account access, then define who looks after the system.

    What we agree together

    A handover list, documentation and agreed issue-fix or maintenance scope

Code ownership, data migration, hosting, external costs and post-handover support are defined in the proposal and agreement before development starts.

04 / Getting started

Tell us about the work
you want to improve

You do not need a complete feature list. Tell us where the work gets stuck, who uses the system and how it works today. We can work through the details together.

  • The task or workflow you want to change
  • User groups and the people accepting the work
  • Example forms with personal details removed
  • Existing systems, timing and constraints
Open the project checklist
Can we start with an existing system?

Yes. We review the current scope, data formats, access and constraints before assessing whether to extend it, connect it or build separately. Migration needs its own checks and an agreed scope.

Do we need a complete brief or terms of reference?

A workflow, example forms and user groups are enough for an initial conversation. We then agree scope and deliverables, taking the organisation’s procurement process and requirements into account.

Questions about pricing, code and support

Which part of the work
would you start with?

Tell us about the system your team needs. We will work out an approach and scope together.

Monday–Friday, 09:00–18:00 Thailand time

Discuss your school system