How we work · Agile by default
Partnership-driven development. Not handoffs.
Custom development at A4IT means more than writing code. We become your technology partner, working closely across every phase to align solutions with business objectives. Agile by default — transparent, flexible, and built to deliver value continuously.
Four steps Values Engagement models The first month What we ask of you FAQ
Four steps The same for a website, an integration or an AI pilot
01
Discovery & planning Deep collaboration to understand your challenges, goals and constraints. We define scope, architecture and success metrics together.
Understand the business first
Who uses it, what it replaces, what it may cost and what happens if it is late. Technology comes after that.
Scope you can read
A short document in plain language: what is in, what is out, and which assumptions we made.
Architecture sketch
Systems, data flows and integrations on one page, including what already exists and stays.
Success metrics
How we will both know it worked — agreed before the first line of code.
A backlog in your words
User stories with acceptance criteria that a business owner can check without a developer next to them.
Most valuable first
The order is yours. We advise on dependencies and risk; you decide what matters most.
Clear deliverables
Every sprint has a goal that fits in one sentence and a result you can open.
Room to change
New insight goes on the backlog and is weighed against what is already there. Change is planned, not fought.
A demo every sprint
Working software on a test environment you can reach, not screenshots in a presentation.
Tested as it is built
Automated tests, code review and a build pipeline from the first sprint, so the last week is not a rescue.
Decisions written down
Why something was built the way it was, kept with the code and the tickets.
Problems reported early
When something takes longer or turns out differently, you hear it that week, with options.
A planned go-live
Data migration rehearsed, a fallback agreed, users informed and trained.
Documentation that is used
For users, for administrators and for the next developer — each as short as it can be.
Handover without lock-in
Source code, accounts and credentials are yours. Another party can take over if you want that.
Support after go-live
Fixes, updates, monitoring and small improvements for as long as the solution is in use.
Three values How it feels to work with us
01
Direct communication
Work directly with Tim and the core development team. No middlemen, no miscommunication — just clear, direct collaboration.
02
Complete transparency
Full visibility into progress, challenges and decisions. Regular demos and access to environments keep you informed.
03
Flexible adaptation
Agile by design — adapting to changing requirements and market conditions while maintaining momentum and quality.
Engagement models Agreed in writing before work starts
Model Best for How it runs You decide
Project A defined result: an application, an integration, a migration, an AI pilot Discovery, then sprints with a demo each time Priorities per sprint; when it is good enough to go live Role A project manager, business analyst, functional analyst or developer inside your team Part-time or full-time for an agreed period, in your tools and rhythm The work itself; we bring the experience Ongoing Maintenance, hosting, monitoring, marketing and continuous improvement A recurring arrangement with a regular review What gets attention next; when to stop
Rates and terms are part of the proposal; the general terms are on the legal page .
What a first month looks like An illustration · the real plan follows the discovery
Week 1
Kick-off, access to systems, conversations with the people who do the work. First version of scope and architecture sketch.
Week 2
Backlog and priorities agreed. Environments, repository and build pipeline in place. First sprint starts.
Week 3
First working part on a test environment. Open questions answered with something to look at.
Week 4
First demo and review. Plan adjusted to what we learned; next sprints confirmed.
What we ask of you Partnership has two sides
One person who can decide on priorities and is reachable every week
Access to the people who do the work today, not only their manager
Real examples: documents, data, screens, exceptions
Feedback on each demo within a few days
Access to the systems we need to connect to, or to whoever manages them
Openness about budget and deadlines, so advice fits reality
01 Do you always work agile? By default, yes: working software over ceremony, customer collaboration, responding to change. Where a contract or a regulator needs a fixed plan and formal documents, we deliver those as well.
02 How long is a sprint? Usually two weeks. Short enough to correct course, long enough to finish something worth showing.
03 Can you work with our own developers or agency? Yes. A4IT regularly fills one role in a larger team, or builds one part next to another supplier.
04 Who owns the code? You do, once it is paid for, as set out in the agreement. Repositories and accounts are opened in your name wherever possible.
Ready to start with step one?