01
General inquiries
Introductions, questions about the studio's practice, or informal correspondence that does not yet concern a specific engagement. General messages receive a considered written reply.
Volume IV — Correspondence§ 04 / Contacts
Contacts
A written line
is the way in.
The studio is small and prefers correspondence in writing. Details for reaching us are listed on this page. There are no forms and no automated replies.
Company details
Company
Flash 4 GmbH
Email
schneiderlena496@gmail.com
Website
flash4group.com
Language
English · Deutsch
"Please write. Include the context, the problem, and the outcome you have in mind. A useful reply is easier to compose when the question has already been thought through."
Categories of correspondence
Four kinds of message.
02
Project discussions
Prospective engagements. A short summary of the business context, the problem, and the outcome you are trying to achieve is enough to begin. We do not require a full specification before speaking.
03
Technical consultations
Focused technical questions — architecture review, technology choice, or a second opinion on an existing plan. Short paid engagements are available where a considered written answer is what the client actually needs.
04
Business cooperation
Partnerships with adjacent firms, subcontracting arrangements, and long-term collaboration with agencies, consultancies, and product companies that need dedicated engineering capacity.
Response process
How correspondence is handled.
- 01Every message is read by a member of the studio, not a filter.
- 02A written reply follows within a small number of business days.
- 03If the enquiry is a fit, a short conversation is arranged to explore it.
- 04If it is not, we say so honestly and, where possible, point elsewhere.
- 05Anything shared with us in confidence stays in confidence, regardless of outcome.
Before writing
A short checklist for a productive first message.
- 01A brief description of your organisation and the domain you operate in.
- 02The specific problem, decision, or outcome that prompted the enquiry.
- 03The existing systems or teams that the work would touch, at a high level.
- 04Any hard constraints — timing, budget envelope, regulatory, technology.
- 05Whether the engagement should be a fixed-scope build, a retainer, an embedded team, or an advisory consultation.
- 06The names of the people who will make the decision on your side, so that correspondence stays with the right person.