Business system
Case study: Trafik ExpresszTrafik Expressz
A sales support system on SAP Business One, running on tablets and phones for a nationwide field sales team.
IT project specification · Discovery phase
IT project specification, before a single line of code.
Got an idea or a process that has stalled, but no precise description of it yet? Before development starts, we run a separate discovery phase: together with one of our business analysts we gather every requirement and write a software requirements specification, with written requirements, visual designs and a system design. It shows you what we will build, how long it will take and in what order.
- months for a typical specification
- 1–1.5
- week sprints during development
- 2–3
- projects delivered since 2013
- 200+
Complex SAP integration, planned up front
When do you need it?
Without a precise description, you can't ask for a quote with confidence.
Most software projects don't go wrong in the coding. They go wrong because the client and the developer read the same sentence differently. Without a precise specification every quote is a guess, and what was left out only surfaces halfway through. An IT project specification removes that uncertainty before development begins.
With us, specification is a phase of its own, separate from development. Through guided questions and joint meetings we map every function and behaviour of the system, from a business and an IT angle at the same time. At the end you have the requirements specification, the visual design and a development roadmap, so any quote for the software development rests on solid ground.
Typical situations that bring people to us
- You can't ask for a quote with confidence because you have no precise description
- You worry you won't end up with what you actually wanted
- You have an idea but don't know whether it can be built
- You need guided questions to pull your project together
- Several systems need connecting and you don't know where to start
What you get
Documentation you can build from.
A specification ends in a visual document and a written one that together cover every requirement of the project. Where needed we work out the technical details too, so on the first day of development everyone is looking at the same plan.
Clarified business needs
We pin down the goals, the users and the processes together, so the system solves a business problem rather than ticking off a feature list.
Requirements specification
Every functional and non-functional requirement written down: what the system does, for whom, under which rules, and what standards it has to meet.
Visual design, wireframes included
Screen designs and user journeys that show how the interface will work before development starts, thought through from a UX/UI perspective.
System design and technical detail
Where needed, we work out the architecture, the data and the integrations, such as connecting an existing ERP or CRM system.
A roadmap you can follow
Prioritised features broken down into sprints. Once the exact requirements are known, the project is far easier to estimate and deadlines are easier to keep.
A clear view of feasibility
An expert team explores the options: what can be built, what a sensible first version looks like, and what can wait for a later round.
Our work
Complex systems, live in production
A sales system built on SAP Business One, a development plan we put together from the client's existing materials, and a language learning platform we have been building for 10+ years across five major versions.
Education
Case study: gotomarketing.hugotomarketing.hu
A subscription-based learning platform with hundreds of video lessons and masterclasses, on any device.
Education, language learning
Case study: XeropanXeropan
Playful language learning with AI conversations for 5 million learners. The official language learning module of Hungarian public education.
What these projects show
- Trafik Expressz
- Three interfaces on one SAP Business One back end: tablet app, B2B web shop, mobile app
- Built on Firelight Kft's existing ERP, without replacing it
- Route planning, sales figures, store visits and sales in one system
- gotomarketing.hu
- We put the development plan together from their existing materials
- In Wolf Gábor's words, the team “practically briefed themselves”
- A custom web app with iOS and Android apps, replacing a WordPress site
- Xeropan
- 10+ years of working together, across 5 major versions
- Web learning platform and iOS/Android apps for 5 million learners
- KRÉTA integration for 200,000+ students
How we work
Business and IT thinking, at the same table.
One of our business analysts leads the specification, and our developers take part too, so whatever goes on paper can actually be built. We tailor the process to your project: the team's make-up and capacity follow what you need.
Business and IT perspective
We look not only at what can be built but at what is worth building: what adds value in the first version, and what can wait.
Business analyst and developers
A business analyst gathers the requirements and our developers work out the technical questions, in the same process.
Clear, readable documentation
You get a document anyone in your company can follow, not just a developer. Full transparency, no hidden detail.
Guided questions
You don't need to know what to write down. We ask, you talk about your business, and the plan comes together from that.
Our process
Where specification fits in
Specification is the second step: after the first consultation and before development. Then we prioritise the features and usually deliver the system piece by piece in 2–3 week sprints.
01. step: Business and technical discovery
We get to know your business goal, your current processes and the technical constraints before we talk about any solution.
02. step: Specification and solution design
We put together a concrete, documented plan: what we build, with which technology, on what timeline.
03. step: Iterative development
We work in short cycles with regular feedback points, so anything that needs correcting shows up early.
04. step: Testing and rollout
Thorough testing and a controlled rollout make sure live use goes smoothly.
05. step: Long-term support
Delivery is not the end, it is just the beginning. We maintain, extend and scale the system through your next business stage too.
- for a typical specification, depending on project size
- 1–1.5 months
- per development sprint, followed by a progress demo
- 2–3 weeks
Technologies
The plan covers the technology too
During specification we also recommend the technology the system should be built with, matched to the size of the project, your existing systems and your budget, not to fashion.
- Web front end
- ReactNext.jsVueTypeScriptViteTailwind CSS
- Back end
- Node.jsRuby on RailsMoleculerFastifyREST APIs
- Mobile
- Swift / SwiftUIKotlinReact NativeExpoFlutter
- Databases and messaging
- PostgreSQLMySQLMongoDBRedisSupabaseRabbitMQKafka
- Cloud and DevOps
- AWSGoogle CloudFirebaseHerokuCoolifyDockerKubernetesBitbucket Pipelines
- AI
- OpenAIAnthropic ClaudeGoogle GeminiAI integration and automation
Debrecen and Europe
In person or online, whichever suits you
A specification involves a lot of conversation, so we are happy to meet in person: our office is on Simonffy utca in Debrecen. Our clients come from all over Hungary, though, and requirements workshops work just as well online.
We work in English too, so we can write the documentation with international teams or a parent company abroad.
- working together since
- 2013
- working languages
- HU · EN
FAQ
What people ask about IT project specification
If your question isn't here, bring it to our first conversation.
01
What is an IT project specification?
It is the planning phase before development, in which we describe every function and behaviour of the system. The result is a software requirements specification: a written document with the functional and non-functional requirements, a visual design and, where needed, a system design with the technical details.
02
How long does a specification take?
Typically 1–1.5 months, but it depends heavily on the size of the project: on how much time and effort it takes to uncover every requirement together with our business analyst.
03
How much of my time will it take?
We need you to be available during the specification, because we gather the requirements in joint meetings. If you already have materials, we work from those too: for gotomarketing.hu, for example, we put the development plan together from their existing materials.
04
How much does an IT project specification cost?
It depends on the size and complexity of the project, so we don't quote off the cuff. We start with a free consultation to talk through what you need, and then give you a proposal for the specification.
05
Will I get a more accurate quote for the development afterwards?
Yes, that is one of the main points of a specification. Once the exact requirements are known, we break the project into sprints and follow a roadmap, so the cost and schedule of development are far easier to estimate than from a few lines of description.
06
I have an idea but don't know if it can be built. Can I still get in touch?
Yes, that is a typical starting point. The specification shows what can be built, what belongs in the first version and what can wait, before you put serious money into development.
07
What happens after the specification?
We prioritise the features and usually develop in 2–3 week sprints. The first sprint or two is mostly groundwork; after that we typically show you progress in a demo every one or two sprints. Development is followed by testing and a beta period, then launch and long-term support.
Related services
What comes after the specification
Custom software development
Business software, CRM and ERP integration, AI automation.
Take a lookWeb app development
Customer portals, SaaS, subscription platforms and admin systems.
Take a lookMobile app development
iOS and Android apps from concept to operation.
Take a lookCodeYard Studio
A permanent product team on a fixed monthly budget, for live products.
Take a look
Contact
Got a business problem you'd solve with software?
Let's talk. We'll help you see the options and find the solution that fits you best.
- Free consultation
- Quick response
- Straight, expert answers
Or write to us directly: business@codeyard.eu
