Ik ben van plan om met mijn ontwikkelteam de Nederlandse markt te betreden. We staan ​​echter voor een aantal uitdagingen, te beginnen met de taalbarrière. Ik ben momenteel op zoek naar iemand die in Nederland woont en mij wil ondersteunen. Programmeervaardigheden zijn een pluspunt, maar niet vereist. Beheersing van meerdere talen is bijzonder wenselijk. Dit is geen kortlopend project; ik zoek iemand die een langetermijnvisie deelt. Het gaat hier niet om gratis werk. We kunnen de details via DM bespreken. Ik stel een snelle reactie op prijs.

I've been doing residential design in California for about 30 years. If I could hand my younger self a short list, it wouldn't be "collect more resources" it'd be the few that actually change how you work: Revit is my main tool - worth going deep on rather than spreading thin across five programs. - For learning it well, the Revit Kid, Balkan Architect, and The Street Architect (YouTube) are the ones I'd actually follow. - A Pattern Language by Christopher Alexander not a software or drafting book, but the best thing I know for understanding why a space actually works for the people in it. It'll make you a better designer, not just a better drafter. - UpCodes or ICC Digital Codes so you're working from the actual CRC instead of guessing what the city wants. - AIBD (American Institute of Building Design) the professional home for designers who do this work without being licensed architects. Worth a look. But here's the real answer to "how do I improve my services to clients," and it's not a book. Years ago I designed an addition onto an existing garage a clean solution, I was proud of it. Right before submittal, I found out the neighbors had sold their property. The new survey moved the property line, and suddenly my setback was cutting the corner off the building. I'd trusted the existing information instead of verifying it myself. I had to redesign the whole thing, and the client was never happy with the compromised version. That mistake cost me time, money, and a client's trust. What it taught me: verify everything yourself. Measure, then measure again. Out in the field it's not always what you see on paper, and the assumption you didn't check is the one that comes back to bite you. The corrections and the close calls are the real curriculum that's what actually makes you better at serving clients. Happy to go deeper on any of this if it's useful.

Currently I am working as senior software engineer and founder, I am looking for a partner based in Netherlands. For expanding my development business and cooperation with partner, I have clear idea. Programming skills are preferred but not mandatory. Let's talk in dm in more details.

I’m Ayan. Currently on a gap year and planning to pursue architecture. I’m really interested in design and want to learn more about the field before starting. Looking forward to connecting and learning from you all!

You didn’t survive studio all-nighters, crit reviews, and years of licensure exams just to negotiate your fees down on Zoom. But a lot of firms are still: Waiting on referrals Hoping brokers send something Sending proposals and getting ghosted Hearing “we’re talking to other firms” and feeling pressure That’s not strategy. That’s survival. And survival mode is expensive. If your average project is $80k–$120k and you’re closing 2 out of 10 qualified inquiries, that’s not a design issue. It’s a structure issue. The firms dominating their market aren’t always more talented. They just: Control the discovery call Pre-frame budget early Anchor value before fees Filter bad-fit clients Follow a defined sales process Most architects were never taught how to handle fee objections, prevent scope creep, or build authority so clients come in pre-sold. So they discount. They tolerate red flags. They take projects they don’t even love. And they think it’s normal. It’s not. Architecture school taught you how to design. Nobody taught you how to win. This isn’t a talent gap. It’s a skill gap.