Starting software as “we will code, then we will see” is expensive. At Bitdyno we write who uses which screen first. Sales and finance should not share the same table. Drawing UI before that is like skipping the wireframe in design.
The definition sits in what is web software">what web software is. Here there is an order: business rule, roles, screen skeleton, development slices, test, go-live, care. Each slice has acceptance criteria; otherwise the job becomes endless revision.
1. Analysis and acceptance
What does “approved” mean on a booking? Payment in, room blocked, mail sent? Those sentences are written in language people speak before they enter code. If there is an integration, the other side’s fields are listed in this round too.
2. Skeleton and permission
Which menu is open to whom? Who may delete a draft? If there is a customer-facing screen, the login path is planned so it does not collide with the marketing site. Look still talks to the how web design is done">design process; button colour does not change the rule.
3. Slices, test, live
- Small deliveries: list and record first, then reports, then automation.
- Test: happy path and failure path; form and permission breaks.
- Live: backup, monitoring, whose accounts get opened.
- Care: when the rule changes, the screen changes; it is not written once and forgotten.
If a phone channel opens, the how mobile apps are built">mobile process should use the same rule glossary. Scope is on web software">web software; quotes via the contact">form.
Tests go blind if acceptance is not a written sentence
Bitdyno does not run software as “show a screen, code if they like it”. First, acceptance: in which state the system does what, and what it refuses. Without project brief guide quality, test day defends three truths. Definition: what is web software">what web software is. Production: web software">web software service. Code is not piled before the window sequence in how web design is done">how web design is done.
A permission matrix is drawn in discovery. Personal data sits with privacy and legal compliance. The panel URL does not open “because we are inside” without HTTPS and SSL. Backup and rollback belong to maintenance and security, not launch heroics.
What the first slice takes live, what it deliberately postpones
The first slice is the narrowest path that stops Excel. Ten reports, three integrations and an app in one sprint ship nothing. Slicing honours the threshold in what is web software consulting">web software consulting. Cart and returns, if they exist, are measured early (cart abandonment). Hosting (choosing the right server) is not buried under the slice.
- Happy path: record, state change, notice.
- Failure path: double click, timeout, unauthorised try.
- Training copy: “approve” has one meaning.
- Measurement: analytics reading guide does not mix window events with panel events.
- Panel uploads follow image optimization too.
Training day must not invent a new rule
Go-live opens accounts, stops the old sheet, splits marketing login from panel login. Domain (choosing a domain name) is not decided that morning. A mobile face uses how mobile apps are built">how mobile apps are built and the same glossary. Window SEO is how seo is done">how SEO is done; Search Console guide watches that the panel stays out of the index. No public price list. contact">contact form. Examples references">references.
A panel does not go live without a permission matrix
Bitdyno does not accept “give everyone admin, we will tidy later”. The matrix is drawn in discovery: who deletes, who sees price, who exports, who only reads. Without it, training day makes everyone a superuser and a privacy incident looks like an operations slip when it was a design choice. If the log cannot answer “who changed this”, care goes blind. Backup owner and rollback minutes are the field face of the definition, not sprint decoration. The first slice stops Excel. The second does not inflate reports. A holding approval chain, a hotel channel manager and a shop coupon are different rows. If a mobile face opens, the same row is translated into the app glossary. Staging does not carry live customer records. If hosting suffocates under this matrix, a cheap label costs more than the window ever will.
Three questions that land during production
Do staging and live share the same data?
They should not. Customer records get deleted in training; copies stay separate.
What if a plugin says “this will be quick”?
WordPress versus custom software opens again. If the plugin does not speak your sentence, it creates debt.
Can design change after the first slice?
The window can. The rule glossary should not, unless acceptance is rewritten.
What is checked on go-live day?
Backup taken, whose accounts opened, old Excel stopped, marketing login mixed with panel login? That list is part of web software service. Domain choice can be separate but SSL is mandatory on the panel URL too. Care does not stop because “we launched”.
Why operations copy is as much work as code
What does “approve” approve? When does the customer mail go? Those sentences must sit in the same glossary as the definition piece. Otherwise training day invents a new rule. If a mobile face opens, it uses the same glossary.
Scope is set in discovery; there is no public price list. Write via the contact">contact form.
What goes live in the first slice?
List, record, basic permission. Reports and automation are slice two. Hosting and backup sit in the same sentence as cheap hosting costs more choosing the right server / website maintenance and security guide after launch. Domain how to choose the right domain name for your business can be separate; the login URL must not collide with the window.
What does test mean?
Happy path is not enough. Unauthorized delete, double charge, broken network, old browser. Analytics analytics guide stop celebrating the wrong metrics does not celebrate sessions on a software screen; it asks if the job finished. Mail notices, if they are ops, are written in discovery — email marketing guide your list is worth gold.
FAQ
Can software start before design ends?
The rule glossary yes; pixels no. Look walks with how web design is done.
Related pages on Bitdyno
Read this guide together with the service, academy and blog pieces that share the same discovery. Links stay on this site.
- web software">Web software service
- what is web software">What is web software?
- how mobile apps are built">How mobile apps are built
For a live project use the contact">contact form. Shipped work sits on references">references.
