[{"data":1,"prerenderedAt":142},["ShallowReactive",2],{"work-hcit":3,"work-siblings-hcit":104},{"id":4,"title":5,"accent":6,"body":7,"completedAt":85,"cover":86,"coverAlt":87,"description":13,"extension":88,"external":89,"liveUrl":89,"meta":90,"navigation":91,"order":92,"path":93,"role":94,"seo":95,"stack":96,"status":99,"stem":100,"summary":101,"year":102,"__hash__":103},"work\u002Fwork\u002Fhcit.md","HCIT","#7c2d12",{"type":8,"value":9,"toc":77},"minimark",[10,14,19,22,41,45,53,59,62,70,74],[11,12,13],"p",{},"Hello CIT sells infrastructure, AI agents, telecom, custom software, and cybersecurity, and named\nevery one of them starting with the same word. That naming decision is either the thing that\nmakes five unrelated service lines read as one company, or the thing that makes a visitor scroll\npast all five without remembering any of them. The site had to make it the first one.",[15,16,18],"h2",{"id":17},"the-problem-underneath-the-brief","The problem underneath the brief",[11,20,21],{},"An integrator selling to enterprise buyers has one job before anything else: prove it belongs in\nthe room with Nvidia and HPE, not just that it resells their hardware. That proof cannot live in\na paragraph of copy, because every integrator's paragraph says the same thing. It has to live in\nthe structure of the page, in how fast a buyer can see the certifications, the client roster, and\nthe specific vertical they came looking for.",[23,24,25,31,36],"metric-row",{},[26,27],"metric",{"label":28,"note":29,"value":30},"Service verticals","Hello Infrastructure, Hello Agents, Hello Phone, Hello Code, Hello Cybersecurity.","5",[26,32],{"label":33,"note":34,"value":35},"Featured solutions","AI Factory, AI Agents, and Digital Power sit above the vertical list, not inside it.","3",[26,37],{"label":38,"note":39,"value":40},"Enterprise client logos","Nvidia, HPE, Huawei, Lenovo, Fortinet, Check Point, and Commvault, all above the fold.","7",[15,42,44],{"id":43},"how-it-is-built","How it is built",[11,46,47,48,52],{},"Next.js on the front end, with ",[49,50,51],"code",{},"next\u002Fimage"," doing the heavy lifting across the client logo wall\nand the hero, where a dozen vendor marks and a rotating solutions banner would otherwise be the\nslowest thing on the page. The page order was the real design decision: solutions overview first,\nthen the client logos and testimonials, then the FAQ, then team bios, with the blog and contact\nforms doing the closing work at the bottom.",[54,55],"shot",{"alt":56,"caption":57,"src":58},"The five Hello service verticals rendered as a grid, each linking to its own detail page.","Same prefix, five different buyers. The grid has to let a visitor searching for cybersecurity ignore the four verticals that aren't theirs.","\u002Fwork\u002Fhcit\u002Fshot-services.png",[11,60,61],{},"Putting the certifications, ISO 9001, ISO 37001, NVIDIA HPC, PMI, ITIL v4, and Huawei HCSA, in\nthe same visual register as the client logos rather than buried in a footer was the other lever.\nA certification list reads as compliance theater on its own page. Beside the Nvidia and Huawei\nmarks, it reads as evidence for the claim the logos are already making.",[63,64,67],"callout",{"title":65,"tone":66},"The naming risk that paid off","accent",[11,68,69],{},"Five sub brands sharing one word is a bet that consistency beats specificity. It only works if\nthe page lets someone skip straight to their vertical in one glance, which is a layout problem\nbefore it is a naming one.",[15,71,73],{"id":72},"what-i-would-keep","What I would keep",[11,75,76],{},"Ordering the page around proof before pitch. An integrator's buyer already knows what an\nintegrator does; what they are checking is whether this one has done it for a company their size,\nwhich is exactly what the logo wall and the certification list are there to answer.",{"title":78,"searchDepth":79,"depth":80,"links":81},"",2,3,[82,83,84],{"id":17,"depth":79,"text":18},{"id":43,"depth":79,"text":44},{"id":72,"depth":79,"text":73},"2025-11","\u002Fwork\u002Fhcit\u002Fcover.png","The Hello CIT home page, showing the five Hello service verticals above a row of enterprise client logos.","md",null,{},true,4,"\u002Fwork\u002Fhcit","Front end build",{"title":5,"description":13},[97,98],"Next.js","React","completed","work\u002Fhcit","A five vertical AI and infrastructure integrator whose site had to make enterprise grade credibility legible without turning into an alphabet soup of sub brands.",2025,"cTT5liJ1ThIIrb5lFBuALGhykExdVjlTf343A27rA9k",[105,109,113,117,118,122,126,130,134,138],{"path":106,"title":107,"summary":108},"\u002Fwork\u002Fwayta-peru","Wayta Perú","A bilingual travel operator site where the marketing page, the blog, and the studio the client edits in are one deployment.",{"path":110,"title":111,"summary":112},"\u002Fwork\u002Fpersonae","Personae","A persona library built on IBM Carbon, where every profile links out to its research and every reader can flag a claim that no longer holds.",{"path":114,"title":115,"summary":116},"\u002Fwork\u002Farsonistai","ArsonistAI","An AI design consultancy with two audiences on one homepage, enterprises hiring for AI augmented product work, and individual designers buying tools off the shelf.",{"path":93,"title":5,"summary":101},{"path":119,"title":120,"summary":121},"\u002Fwork\u002Flynne","Lynne","A lead capture first booking site for a solo telehealth counseling practice, sized to get one action in front of a visitor rather than a full site's worth of pages.",{"path":123,"title":124,"summary":125},"\u002Fwork\u002Fn-hub","N Brand Portal","An internal brand portal holding the logos, color tokens, and templates a small team actually needs, so the approved asset stops living in an eight month old Slack thread.",{"path":127,"title":128,"summary":129},"\u002Fwork\u002Freductivist","Reductivist","A minimalist goods brand selling a handful of well made objects, where the real commerce problem was resisting the urge to add a fourth product to the homepage.",{"path":131,"title":132,"summary":133},"\u002Fwork\u002Fpattern-library","Pattern Library","Four hundred and twenty two documented interaction patterns across web, mobile, and cross platform concerns, with the rationale that makes each one work.",{"path":135,"title":136,"summary":137},"\u002Fwork\u002Fflow-society-mx","Flow Society MX","An e-bike tour operator in Jalisco, with a six step booking flow, a per departure availability calendar, and an operator dashboard behind it.",{"path":139,"title":140,"summary":141},"\u002Fwork\u002Fcytron-motorcycles","Cytron Motorcycles","A Tokyo motorcycle brand invented end to end, drawn as a working prototype and then built as the site that prototype had been arguing for.",1789230933861]