◉ FAQ

Frequently asked questions

Concrete answers on how we work, timelines, costs, code ownership, maintenance and everything a B2B client wants to know before reaching out.

01What kind of projects do you take on?+

End-to-end software/hardware integration: RFID cashless, access control, orchestrated backend, operator apps, computer vision, industrial automation, real-time data. We mainly work in entertainment (parks, waterparks, events), industry (instrumentation, metrology, automation) and finance (equity research, analytical terminals).

We don't do brochure sites, off-the-shelf e-commerce, or mass-market consumer apps.

02How long does a typical project take?+

Depends on scope. Real benchmarks:

Discovery + prototype: 2-6 weeks. Output: technical doc, mockups, cost estimate.
Integrated MVP: 2-4 months. One subsystem in production, scalable.
Multi-module platform: 6-18 months. Multiple systems talking, governance, audit.
Continuous partnership: years. See Gardaland (12+).

03How does the engagement model work?+

Three formats depending on problem maturity:

1. Fixed-fee discovery — flat fee to analyze, scope, estimate. Output is client property.
2. Turnkey project — milestones with progress payments. Suitable when scope is clear.
3. T&M / time-and-material — dedicated team, monthly sprints, evolving scope. Suitable for long-term partnerships.

Often we start with (1) and decide together whether to continue with (2) or (3).

04Who owns the source code?+

The client. Always. Code written under contract is client property, delivered in an accessible git repository, documented. No vendor lock-in.

When we use our internal reusable libraries or open-source components, we declare it explicitly in the contract and LICENSE files.

05Do you work on-site or remote?+

Both. The team mainly operates from our office in Grassobbio (Bergamo); on-site is mandatory for: kickoff, hardware integration phases (readers, kiosks, RFID), field testing, go-live, operator training. For pure software development: remote with weekly sync.

For clients abroad (e.g. Future·Tech in Japan) we work mostly remotely with focused trips.

06What happens after go-live? Maintenance and support?+

We offer structured maintenance contracts in three tiers:

Bronze — critical bug-fix, business hours window.
Silver — bug-fix + minor evolutions, guaranteed SLA, monitoring.
Gold — dedicated team, continuous evolution, 24/7 on-call for critical systems.

Tier is decided together based on system criticality and volumes.

07What if I switch providers? Exit strategy?+

The code is yours from day one. Every project includes: technical documentation, operational runbook, formal knowledge transfer to the new team. We guarantee 1-3 months of side-by-side handover with the incoming partner. Architectures are designed to be picked up without depending on us.

It's a commercial principle for us: selling lock-in is a shortcut, building trust pays better long-term.

08How much does a project cost? Do you have a price list?+

We don't have a catalog of off-the-shelf modules because every integration is different. Reference figures:

Fixed-fee discovery: from €5,000.
Integrated MVP: €30,000 to €120,000.
Multi-module platform: from €150,000.
Maintenance: from €1,500/month.

We always provide a detailed estimate after discovery, never surprise figures mid-project.

09Who will I actually see on the project?+

Boutique <30 people: the same people who sell are the ones who design. Founders are directly accessible throughout the relationship. No intermediary account managers, no sales PowerPoint followed by anonymous junior team.

For each project we appoint a tech lead as single point of contact, supported by 2-5 engineers based on required skills.

10How do you handle sensitive data and compliance?+

EU-only servers (no extra-EU transfers). Encryption at-rest and in-transit. Immutable audit logs on systems requiring them. For payments we follow PCI-DSS. For personal data GDPR by design. For fiscal receipts RT/XML.

No client data leaves the boundaries agreed in the DPA (Data Processing Agreement) signed with each client.

11What technology stacks do you use?+

Pragmatic stack, chosen by problem:

Backend: Node.js, .NET, Python, Go.
Frontend: React, Vue, native mobile (Swift, Kotlin).
Embedded: C, C++, Rust on microcontrollers and SBCs.
DB: PostgreSQL, MS SQL, Redis, time-series (Influx, Timescale).
Cloud: AWS, Azure, hybrid on-prem.

Not religious about any framework. We pick what the problem needs.

12How do I get started? What happens after I write?+

Write to info@brkt.it with two lines about the problem (no need for more).

Step 1 (within 24h): reply with any clarifying questions.
Step 2 (within 1 week): 30-45 min exploratory call with a founder.
Step 3: discovery proposal if the problem is in our wheelhouse, honest redirect elsewhere if it isn't.

We say "no" if the project isn't for us: better for you, better for us.

Question not in the list?

Write us → info@brkt.it