Skip to content
A new build starts every Tuesday.

Sample build brief

Version 1.0 · 19 October 2026

Klantportaal

Start
Tue 10 Nov 09:00
Live
Mon 16 Nov 17:00
Price
€11,000 excl. VAT
€13,310 incl. VAT

Version 1.0 of 19 October 2026

Sample. This Build brief is fictitious and binds no one. The dates are those of the first free build week.

Between Sounds Global B.V., trading as AppIn7Days, KvK 88875539 (AppIn7Days), and Voorbeeld Installatietechniek BV, Voorbeeldweg 1, 7550 AA Hengelo (NL), KvK 00000000 (the Client).

Project: Klantportaal · Build brief version 1 · AppIn7Days rules v1.87, BLAKE3 digest b86f0cd5e2657537f244285e2af77a3c2adb53b86a45b3a829e8a1aa4808acd7 · Partner: none.

There is no translation; you are reading the binding English text.

1. Goal and scope

Customers see for themselves where their order stands, with its work orders, invoice and documents, and ask a question about it without calling.

1. Goal and scope
PortalAddress
Klantportaalhttps://portaal.voorbeeld.example
Binnendiensthttps://binnendienst.voorbeeld.example

Editions of the Native app, per portal:

None; the app works in the browser on computer, tablet and phone.

No price in this Build brief includes a developer account. Every account an Edition of the Native app requires belongs to your own organisation, in its own name, and you pay the provider yourself, as article 9.16 of the terms and conditions says.

Always included (article 9.10 of the terms and conditions): Texts and images, Management area and Organisation management. With Texts and images, your Organisation changes any text and image of the app itself. With Management area, your Organisation manages its own records, lists and settings, within the standard limits. With Organisation management, your Organisation's own admin invites members, gives them their roles and removes them.

This summary comes from the specification in article 2. What we build is in that specification.

2. Specification and brandbook

With the Fit check we drafted two documents for this app. They are part of this Build brief and together decide what we build:

2. Specification and brandbook
DocumentVersionBLAKE3 digest
The app's normative specification1.716338c5e330bd2f4f8a3d49295a25f2ccc7939d535123e0eb830ec6462a91b43
The app's brandbook1.5a15dcbea4f6679bde2b40a7e6c7da4272b8d124030c9fb84dd416ca808438d76

The specification describes the roles, the Core process, every screen, the integrations, the data import, what this Build excludes on top of the public Not-list, and every accessibility exception with its reason. For a Native app it names each device capability, and only one proven on that Edition. The brandbook decides what the app's users see.

The Done when criteria in the specification are statements you answer yes or no by using the app. Only they decide whether a Pin is a Bug or a Wish. At most 10 Wishes count on the Feedback list; above that the Swap rule applies, or the Wish goes to the Parking list.

You sign for exactly these two texts: the digest belongs to every character. Before signing you can comment on any sentence; a change that follows is a new version, at no cost. After signing, only an Amendment changes them.

3. Decision maker

The Decision maker is the person who signs for the Client, as managing director. On signing, the Decision maker confirms that they may bind the Client.

This Build brief names no Staff member. The Builder who leads the Build is your only contact with us. You see who that is on the Build's page and in every entry in the Build log.

4. Dates

Checklist complete Mon 9 Nov 17:00. Start Tue 10 Nov 09:00; the Preview is live by Tue 10 Nov 17:00. Demo Wed 11 Nov 17:00; stop button until Thu 12 Nov 09:00. Feedback deadline Thu 12 Nov 12:00; later Wishes go to the Parking list. Test version Fri 13 Nov 17:00; no new features after it. Live Mon 16 Nov 17:00, with the part of the Handover due at Live; the rest of the Handover comes with the code (article 8).

All times are Dutch time. These dates move only through a pause of the Clock, an Amendment or a move to another Slot before Start. If we publish the Demo late, only the stop button's deadline moves, as article 13.4 of the terms and conditions says.

A Native app is Live as article 15.5 of the terms and conditions says, with no promise about approval or publication in a store.

5. Price

5. Price
ItemExcl. VATIncl. VAT
7-day build€9,500€11,495
Messages add-on, in the week of Tue 10 Nov€1,500€1,815

The price is fixed: €11,000 excl. VAT. To pay: €13,310 (incl. VAT). You pay 50% on signing and the rest at Live, each within 7 days. The same applies to every Add-on in this build week, an extra integration included; the table names its first available start. Extra cost arises only from a signed Amendment or from a product you order separately.

Third-party services for an Add-on, as article 9.13 of the terms and conditions governs them:

None.

If a Partner is named above, that Partner introduced you to us. That Partner receives a commission from us of 10% of the price excl. VAT, under the terms of the Partner agreement and only after you have made the second payment. You pay nothing extra for it. This sentence gives the Partner no right of its own.

6. Guarantee and stop button

Until Thu 12 Nov 09:00 the Decision maker may press the stop button. You then get the deposit back within 14 days, minus €1,500 excl. VAT (€1,815 incl. VAT). You then do not receive the code, as article 18 of the terms and conditions says. No decision counts as Approved. If we are late through our own fault, we keep building at no extra cost until Live, and the second invoice comes only at Live.

7. What we need from you

By Mon 9 Nov 17:00 this is done. (1) This Build brief is signed by both parties and the deposit is paid. (2) Test access to the integration is entered through the secret form. (3) Test data or anonymised example files are uploaded. (4) Your logo (SVG or PNG) and brand colours are uploaded. (5) The data processing agreement is signed, if the live app will hold personal data. (6) The Decision maker has confirmed being available on the build days. (7) For a Native app, the developer accounts its Editions need are verified.

On build days you answer a Blocking question within 2 working hours. Otherwise the Clock pauses, and the dates move as article 10 of the terms and conditions says.

8. Licence and ownership

The code is in a private repository of AppIn7Days until the Build is paid in full; until then you use the app as we host it. Within 1 working day after you have paid in full and your Fundamental mirror is ready, you receive the code with its whole history, the README and the deployment files. The IP transfer deed then transfers the copyright and the database right in the code to you, as article 17 of the terms and conditions says. It also transfers the copyright in the specification and the brandbook of article 2. You use Fundamental under the Fundamental licence, version 1.0.

You keep control of your app, and of its code once it is paid in full; you can leave as article 25 of the terms and conditions says. You are responsible for your business conduct and for what you do with the app, as article 30 of the terms and conditions says.

This Build brief comes with the terms and conditions, version 1.0, and the data processing agreement, version 1.0.

9. Next steps

In the Bug window of 30 days we fix Bugs against this Build brief free of charge. It starts at Live, with production hosting. For a Native app it starts at the first store approval, at the latest 30 days after Live, and hosting follows article 16.5 of the terms and conditions.

Then you choose Maintenance Normal: €995 excl. VAT (€1,203.95 incl. VAT) a month, or Maintenance HA: €1,795 excl. VAT (€2,171.95 incl. VAT) a month, each at least 3 months; Keep building: €7,495 excl. VAT (€9,068.95 incl. VAT) per 31 days; or hosting it yourself. Our proposal: none; the choice is yours.

You can switch to another provider or to your own systems at any time, as article 25 of the terms and conditions says. If you do so within Maintenance's minimum term, you pay the remaining months. A prepaid year is not refunded. We charge no switching fees.

This app's infrastructure cost (C) is within what the Maintenance price covers (article 19.12 of the terms and conditions), so no surcharge is added.

You receive every line of C on request, and with every new measurement that changes the price (article 19.14 of the terms and conditions). If this Build is a Native app, the hours on the leased Mac and the upkeep in the stores count in C. The prices above then apply from the end of its Bug window; until then the Apple surcharge, where it applies, covers the Mac.