Skip to main content
x

Interview with Jens Hagel, Founder & Owner, kjello

Interview with Jens Hagel, Founder & Owner, kjello

(Featured) - The Hamburg IT founder discusses integrating acquisitions, separating teams, documenting responsibilities, and using Microsoft 365, Intune and Autopilot.

Edited by Jenn Moon, Editor at Featured News · Nov 16, 2026

As founder and owner of a computer-networking firm in Hamburg, what kinds of business-change IT projects have given you the clearest view of what companies get right — and wrong — when their structure changes?

What I have learned from quick buyouts is this: A company that owned several properties in Hamburg had taken over 22 companies in the span of two years. Users had administrative rights, and two-factor authentication (2FA) was disabled.

We offered them a support package of around 20 hours a month to help them help themselves. Most of this time went towards configuring Autopilot and Intune, Microsoft’s way of deploying and managing devices. Once this was done, all users had 2FA enabled, and new starters could be configured in minutes.

What path led you to build kjello and become the IT partner companies call when they are acquiring, separating, merging or rapidly scaling their operations?

I started hagel IT from my living room in 2004. We migrated to the cloud in 2013. We moved away from hourly billing to a fixed monthly price in 2019. We are now a team of 32 supporting over 150 companies in northern Germany.

Whenever a company changes, staff join and leave. Devices and permissions need to follow suit. kjello was our answer to that. The company can choose a laptop from our portal, and it will be delivered to the employee and configured on first boot. If someone leaves, we can begin disabling their access through our system.

When a client buys another business, what is the first IT discovery step you take to reveal the risks that could disrupt the combined company?

I like to conduct a cyber risk assessment with the managing director and then review the company’s infrastructure to find out where they stand with their newly acquired company.

A company in Bremen bought a specialist company with 18 employees. All employees worked on private laptops with admin rights. The company had terabytes of data on network-attached storage (NAS) with no backups, which would have been difficult to recreate. We moved everything to SharePoint within four weeks and restricted access. The managing director stated that he did not know how close they were to disaster.

From your experience, what information should an acquiring company document before deciding which systems, networks and user accounts to integrate or retire?

Document who has admin rights, what licenses you're paying for and where data is stored. Having admin rights will cause you the most headaches.

An investment company in Hamburg was removed from the group IT department of a larger asset manager. Because the group could not give them access to their Microsoft tenant due to password restrictions, we created a new Microsoft tenant for them. Their IT is now around 40% cheaper than what the group charged them.

When a team is being spun out of a corporate group, how do you help preserve the team’s access to the tools it needs without leaving the former parent company exposed?

Have the company being spun out configured independently. If the two companies share logins, it will only cause headaches for both parties.

A consulting company that was taken out of a corporate group had employees working in Hamburg, Frankfurt and at home. All their laptops and email signatures were configured through the group’s IT department. We built them a serverless office using Microsoft 365, Intune and Autopilot. Even their private iPhones were included, and they pay us a monthly rate per person.

After a period of fast growth, what IT problem tends to remain hidden longest, and what review can a growing company perform now to uncover it?

Excessive admin rights and missing or untested backups. You may not know there's a problem until something goes wrong.

One of our clients in Hamburg had around four employees when we first started supporting them. They now have over 30. One of their employees did IT as their second job, and everyone had admin rights. Our client told me they did not know if their backups were working. We removed their unnecessary administrative rights, and no one noticed. Always check who has admin rights, and restore a backup from the previous week to see if it works.

Across acquisitions, carve-outs, mergers and growth cleanups, what is the one IT habit you would put in place early to make the next major business change far less risky?

2FA on all logins that support it. When we first start working with a company, they almost never have this enabled.

We started with a law firm that had 11 employees and did not have 2FA. It became one of their top security features. When you're buying a company, you will have multiple logins being created. Having 2FA can limit the damage if login credentials are compromised.

Thanks for sharing your knowledge and expertise. Is there anything else you'd like to add?

Know who is doing what when a group of companies buys a company and keeps its group IT involved. We support one of our clients that has group IT in another country. We are the first point of contact, but we do not have permanent admin rights. So, we had to pass any simple tasks on to the group IT. We felt like we were doing work for them.

We now have these responsibilities documented and have started using time-limited administrator credentials.

About the expert

Jens Hagel

Jens HagelFounder & Owner at kjello

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

Interview with Roman Martynenko, Full-Stack Software Engineer and Founding Engineer

Interview with Roman Martynenko, Full-Stack Software Engineer and Founding Engineer

(Featured) - The founding engineer explains how continuous user research, familiar interfaces and workflow tracing help turn AI experiments into dependable business tools.

Edited by Jenn Moon, Editor at Featured News · Nov 13, 2026

As a full-stack software engineer and founding engineer, how would you describe the problems you focus on solving and the perspective you bring to building AI-enabled products?

Our customers were generating decks for their deals mostly by hand. They had tons of spreadsheets and other documents in different formats, with no clear source of truth. They dealt with that chaos every time they needed a deck and spent a lot of time going back and forth over the information.

They also hired whole teams of analysts and designers to sort through those documents and produce the decks. I built an AI-powered deck generation engine that structured the data and then used it to generate high-quality decks. I also worked on map generation and the front end around it.

That’s the kind of problem I focus on: a task that takes people a lot of time because the information is messy and the process is manual. My full-stack background lets me work on both the generation engine and the interface customers use. In this project, I needed to address the data behind the deck as well as the deck itself.

What path led you to become a founding engineer working at the intersection of full-stack development, automation and AI-powered business workflows?

My journey started as a front-end engineer at PVD-Technology, my first position in the information technology (IT) field. Frameworks like React weren’t really popular back then, so my main stack was Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), and vanilla JavaScript. Having that narrow focus allowed me to build solid front end expertise, which served as a foundation for my future career.

In my next position, as a full-stack developer at DecisionMapper, I started extending my skill set with backend technologies. I was fascinated by how the whole thing worked end to end. It helped me deepen my expertise and connect the dots in my understanding of building complex applications with heavy data processing and traffic.

My journey in the startup world began at Zocdoc. During that period, I started paying more attention to the business impact of the software I was building, as well as the importance of domain expertise and working with stakeholders. Later, I joined the founding team at Henry AI, where we built AI-driven solutions for commercial real estate. My work included a deck generation engine that helped customers structure their data and automate work they had previously done manually.

When you move from an AI demo to a real product feature, what is the first real user workflow you examine to determine whether AI can genuinely improve it?

Usually, I start with manual tasks where users spend most of their time and cognitive effort tediously going through documents, entering information, comparing it and reconciling differences. These are tasks where I see AI agents helping more and more.

What interests me is that models can do more than parse documents in various formats and consolidate the information. They can also reason about that information, detect possible inconsistencies and anomalies, suggest changes and, with the right permissions, make changes themselves.

Another task that takes a lot of effort for knowledge workers is research. It might mean searching through documents, doing online research or combining both. With Model Context Protocol (MCP) connectors and plugins, models can retrieve more context from third-party services as they work. Instead of following the whole thread of a complex, multi-hour search, the user can review the end result, its citations, and the sources and actions behind it.

From your experience building workflow-level AI systems, how do you narrow a promising but broad AI idea into a first use case with clear business value?

The first and most important thing is to make sure there is a shared understanding of user needs. That involves user research and a lot of communication with the end user. When I talk to customers, I do not try to sell them my product immediately or ask for their opinion about my idea. Usually, people in that situation compliment your intentions to make you feel good. Instead, I ask questions that help me explore their past experiences with their workflows and the main pain points they had to deal with.

It is also critical to verify whether the problem they are talking about is really a problem. Sometimes people get emotional about things that irritate them once in a while, but it turns out they already have a low-effort workaround that works well enough. Such problems may become worth solving at some point, but at the moment, they are unlikely to bring much business value.

When a real customer problem with the highest potential for business value is identified, it is time to scope the first release. It should cover the core user needs in a specific area, but stay narrow enough to be delivered quickly and improved through further iterations.

What design choices have helped you make AI outputs dependable enough for professionals to use in their day-to-day work rather than treat as a novelty?

Product design is crucial to turning an idea into a useful product, alongside the technical implementation. A lot depends on user research: understanding people’s current workflows, needs and habits. Beyond following interface design best practices, we need to know how technical our users are, how comfortable they are with new technology and how willing they are to change established ways of working.

For example, in the deck editor I built at Henry AI, tables were among the most-used components. They could contain financial data, comparison analyses or breakdowns of metrics. We initially introduced a new way to edit them, but our users found it difficult. So we developed an interface that followed familiar Excel mechanics. Our users already spent a lot of time in Excel, and that familiarity made them much more comfortable making the final corrections to presentations generated by the agentic workflow.

Another part of making AI dependable is showing users where the output came from. In my experience, citations make a big difference. Users can check where a particular number came from or where an image was sourced. If the model takes a number from a profit-and-loss (P&L) statement for the wrong period, that is still a mistake, but the source makes it easier to understand and correct. Without it, the user has no straightforward way to tell whether the number came from the wrong document or was invented by the model.

How do you decide where an AI system can act autonomously and where a human checkpoint is essential in a business workflow?

There are two sides to the decision. On one side, it is the user’s call whether they are comfortable with AI developing, improving and executing a decision for them. Usually, if the cost of a mistake is not very high or critical to the business, and users trust the system, they are more willing to delegate the whole process. Otherwise, they are more cautious and want to keep the final approval.

On the other side, the product itself has to be reliable and traceable. What I find critical in AI-driven systems is evals. These are basically tests for an AI system: We provide use cases and check whether the output meets predefined quality criteria. The results help us understand which tasks the system can handle reliably and where human review is still needed.

This testing system is not static. As the product evolves and we discover new use cases or mistakes, we include them in the tests. That way, our understanding of the system’s reliability develops along with the product, and we have a basis for deciding whether to give it more autonomy.

As a full-stack engineer, how have you built reliability, observability and fallback behavior into AI-powered workflows when model outputs or connected systems fail?

Generally, the techniques developed over decades of classic software engineering still apply to AI-powered systems. We need systems that can scale up and down with the load and have enough redundancy to keep operating if an underlying service fails. For observability, I want to trace a user action from input to output or failure. In an AI workflow, that includes the model’s inputs and outputs, calls to connected services, intermediate artifacts, errors, token usage and the cost of a particular run. These records help us understand where something went wrong, even when the workflow involves several systems.

Another useful technique is deploying agents that observe the system while it runs in production. For example, an agent can monitor an internal assistant’s conversations with users and flag possible anomalies or signs of frustration. It can alert a human while the conversation is still happening, giving them a chance to step in. Those signals can also feed into further improvements, including automatically creating evaluation cases from problematic conversations. I would test any resulting changes before applying them to the live system.

For founding teams looking to turn AI experimentation into a dependable product, what is one practical habit you would establish early to keep development grounded in customer value?

If I had to highlight the most valuable practical habit for keeping development grounded in customer value, it would be continuous user research. As I mentioned earlier, it is critical to understand the user’s problem, their past experiences, their pain points and how they try to resolve those pain points. With that understanding, we can dig into the real user problem and then come up with a solution using our ideas and our product.

However, initial research is not enough. It should be a continuous habit. We keep talking to our customers as we solve certain problems for them, but other problems emerge as their workflows evolve with our product and the other tools they use daily. It is still important to avoid simply asking for feedback on our product or idea and instead focus on their past experiences.

Another point is the importance of building trust. It has always been critical to build trust with your customers, but in the AI era, it is becoming increasingly important and difficult as more and more products are driven by large language models (LLMs) with unpredictable outputs that are hard to control. In that situation, we have to be transparent about the capabilities and limitations of the system we build for our users so they do not encounter unexpected results or face risks they are unaware of.

About the expert

Roman Martynenko

Roman MartynenkoFullstack Software Engineer, Founding Engineer

Disclosure: I previously worked at Henry AI as a Founding Engineer, where I helped develop the AI-powered tools discussed in this interview

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

Small offices on Macs taught me to stop treating them as exceptions

Small offices on Macs taught me to stop treating them as exceptions

(Jens Hagel) - Several IT providers had turned down one of our clients because its staff work on Macs, and looking after offices like that changed how I think about managing devices.

Edited by Jenn Moon, Editor at Featured News · Nov 12, 2026

A while back, a 20-person company got in touch with us. All Mac users. They had been to a few other IT companies before coming to us. One even told them straight up, they didn't want to work with Macs.

I get it, but I don't think it was a good decision. I have been working in the IT sector for small to medium-sized businesses in northern Germany since 2004. I have learned more about device management from Mac offices than from most of our Windows clients.

Why they say no

I think most IT companies use software, scripts, etc., that are tailored to Windows. We also did. We only have a limited amount of hardware/software that we use because that is how you give good answers when you have a small team.

Managing a Mac for a business can require additional setup. There are some things you have to change and different ways to update, etc. Someone has to know where these things are. I think for an IT company that only has a few Macs in their customer base, it is easier to say no.

These companies are most likely not even making an IT decision. These are probably agencies or companies that enjoy using Macs. You wouldn't want them to change their work style just because your IT company doesn't want to learn.

What an office full of unmanaged Macs looks like

We had an advertising agency that came to us. 14 people all using Macs. They stored their files on a Linux server, which was in a small server room that in the summer was 38 degrees Celsius. Around 100 degrees Fahrenheit. They used mobile air conditioners to keep it cool. Only one man knew how to manage the server, and he was 76 and almost retired. He stored backups on Blu-rays that he believed would last 100 years. The managing director said he just wanted to be able to go on vacation and not worry about the server breaking.

The Macs were not a big issue. They were all set up manually and treated as personal computers. Nobody knew what was managed on what machine or what would happen if a Mac was stolen.

We took their files and put them on Microsoft 365/SharePoint. Managed their Macs through Apple's business enrollment platform and Microsoft Intune. That server room is now a storage room.

Managing a Mac

Much like Windows, you have your company device that is stored in a central database. Then you have a program that can manage that device.

Apple Business holds the enrollment records for company Macs. Microsoft Intune can then manage those devices. If you purchase your Mac through Apple or an authorized reseller and have it assigned to your company in Apple Business, it can automatically enroll in your mobile device management (MDM) and receive its settings when first turned on. Microsoft has a great article on how to set up your Mac with Intune. Intune can also be configured to require FileVault encryption during setup on supported Macs.

This means your user can unbox a laptop. Sign into their work account and have email and programs ready to go. Your company can manage that device if it gets lost.

When we created kjello, we wanted to support Macs as a normal device. Just like a user can choose a Windows laptop, they can choose a Mac. Both will set up when first turned on.

When I will say no

There are some situations where I will tell my customers that Macs are not the best choice for them.

There is some software that only works on Windows. Accounting programs and some machine controls come to mind. If you need to run these programs on a Mac, you are going to have to find a workaround. Every workaround you add is another thing that can fail. I would not switch a company over to Macs just for IT.

You will need someone on your team that knows both systems, which for an IT company means more knowledge. I think it's worth it, but I can see why some may not want to take on that extra knowledge. Just don't turn away your customers that use Macs.

The last thing I will say is when purchasing your Macs, if you buy a Mac from a store one Saturday, it may not be automatically added to Apple Business. You can add it later, but it's more work. I have found that if you don't do it when you buy the laptop, it may never get added. Always tell your customers to purchase through a vendor that will add the device to your company.

About the author

Jens Hagel

Jens Hagel is the founder and owner of hagel IT-Services in Hamburg, Germany, which he started alone from home in 2004. He has spent more than 20 years running IT for small and midsize companies in northern Germany and now builds kjello, a platform for managed workplace IT.

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

What a Hotel Doorman Taught Me About Building Software

What a Hotel Doorman Taught Me About Building Software

(Daniel Haiem) - By Daniel Haiem

Edited by Jenn Moon, Editor at Featured News · Nov 10, 2026

I recently came across a concept called the doorman fallacy. Someone posted about it somewhere (I can't remember where exactly), but it was so interesting that I made time to look it up. So, advertising executive Rory Sutherland coined the term "doorman fallacy" in his 2019 book Alchemy, and he illustrates it with a hypothetical hotel.

Picture a hotel manager reviewing costs and realizing that the doorman draws a full salary for just opening a door. He figures that if he gets an automatic door, it will save him money. Obviously, the math looks reasonable. The thing is, the doorman was never just opening a door. He greeted customers, hailed taxis for those who needed one, recognized regulars, and kept an eye on who walked in. Yes, the hotel might have been able to save on payroll, but it could risk losing some regulars along the way because they no longer feel welcome, or because nobody is hailing taxis anymore or watching who walks in.

That's the concept of doorman fallacy. You define a role by its most visible task, then you automate it and eventually lose everything else the role was quietly doing. What's funny is that I've seen companies make the same mistake with software for years — even myself — and I didn't know there was a term for it. Now, with AI booming, that mistake is becoming even easier to make.

Ever since automation became a thing, I've heard countless versions of, "Can we just automate this?" Don't get me wrong, some things genuinely need to be automated to make our lives easier. But there are also times when the workflow they want to replace is rarely as simple as the process document says. There are small steps between the obvious ones that most of us overlook, and the worst part is we won't notice them until later, after the gap has already left dents in the whole process. Just like what happened at Klarna. In early 2024, the company said its AI assistant was doing the equivalent work of 700 full-time customer service agents, but by 2025, its CEO acknowledged that the cost-focused approach had hurt service quality, and Klarna began expanding human support again. They didn't abandon AI completely, though. They basically kept the assistant and added people back where quality had slipped. Simply put, AI could handle the visible task, but the quality of the service was the doorman.

I have been trying to avoid the same mistake for the past few years. Whenever automation is in question — because we love to automate — my team and I do a simple exercise where we list every outcome the role touches, not every task it performs.

The questions include:Who does this person talk to?What do they notice that nobody asked them to notice?Which complaints never reach leadership because this person handles them first?

If that list runs longer than the job description, you've found your doorman. And if you do, for the love of God, do not replace them.

Now when it comes to setting an automation for our clients or if the project involves automation, the first thing I do is evaluate it by pricing everything the role or step touches, not just what it costs overall. This leads me to questions like, "What happens to retention, error rates, escalations, and customer trust?" If nobody on the team can answer that, the savings on the spreadsheet aren't real yet, they are merely an attempt to guess.

Now, let me be clear, none of this is an argument against automation. Most of the software we build exists to remove manual work, and much of it should. I am simply reminding founders, developers, and whoever this may concern about the sequence. You have to understand the full job first, then decide which parts the machine should take.

About the author

Daniel Haiem

Daniel Haiem is the CEO at AppMakers USA, a Los Angeles-based mobile app development firm that has helped startups and enterprise brands design, build, and scale mobile and web products since 2014. Dan writes about product strategy, AI in apps, and what it takes to ship software that lasts.

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

Institutional knowledge is the data skill AI cannot replace

Institutional knowledge is the data skill AI cannot replace

(Vinit Rajguru) - The real risk isn’t automation. It’s assuming AI understands your data when nobody in your company does.

Edited by Jenn Moon, Editor at Featured News · Nov 10, 2026

One weekend I was sitting at my apartment playing with my kid, and I saw a video on TV saying artificial intelligence (AI) will replace everything and people are losing their jobs. The rumination started in my mind that I might also lose my job because of AI, and honestly I was scared and stressed at that time, even though I was in a good position at my current role. As always, the mind tries to protect you. Then I started remembering my early days, how I started my career and how I am using AI in my current role. When I got my hands dirty with it, I realized it will not take my job the way I was thinking.

I have been with the same client for almost five years. When I started, I was shadowing someone and they told me to eyeball the data. Then after one month, that person left the company, and no one was there to teach me. I thought I couldn’t handle it because I didn’t know anything about it. I was hired as an ops person to help the organization with day-to-day operations. I honestly wanted to quit. No one was there to help me, and I was getting pressure from different teams including campaign ops, marketing ops, products and engineering.

This incident happened when the team wanted to launch a campaign, and the goal was to send communications to users who don’t have a business account, but we ended up sending it to users who already had a business account. The reason was the type of identifiers (IDs) we were using to identify those accounts — no one knew what those IDs meant.

So I started collecting evidence. Searching Slack to see if anyone knew about certain tables or columns. Digging through Confluence pages. Trying my luck everywhere. The customer data platform (CDP) also had its own reliability issues when data volumes were too large. The data pipeline was set up to run every two hours, falling back to the next cycle whenever a failure occurred. But there was a hard catch: a strict limit of 200 million records. Exceeding that volume broke the pipeline entirely, leaving us with only two paths forward: Either cut down the data volume or contact the CDP support team in advance to give them a heads-up that a specific audience would breach the threshold.

Usually, whenever we received a request from marketing ops or campaign ops or the product team, we had to follow a few steps: Submit a ticket in our project management tool, wait for it to be assigned and then take it from there. Based on these requests, the average end-to-end turnaround time was approximately five days, which became a pain point for the marketing and campaign ops teams. While this timeline was generally acceptable for regular campaigns, ad hoc campaigns often required a faster turnaround.

To optimize this workflow, and after many trials, I engineered an AI-assisted tool (Field Identifier) that lets campaign ops and marketing ops identify which fields they can use for their upcoming campaigns without reaching out to the data team every time.

Did the changes actually make a difference? We let the data speak for itself. In the second half of 2025, our team of three completed 170 requests with an average five-day turnaround. After building and testing a prototype in January 2026, I launched it in February. Over the next six months, despite taking on a higher workload of 185 requests, we cut our turnaround time down to just two days.Field Identifier did a lot of the heavy work, but the speed boost came from a few moving parts working together — mainly automation, better Structured Query Language (SQL) queries and the team tweaking the workflow as we grew. This was our "aha" moment because the dashboard gave leadership visibility into the measurable improvements we had achieved.

Currently, I am architecting an AI agent to fully automate query execution and segment building, so marketers don’t even have to interact with the tool. They simply make a request, and the work gets done. Their only responsibility is to review the result and make sure everything looks correct.

The way I use AI is more like a conversation. I bring my problem, AI asks me clarifying questions, I answer and together we figure things out. But here is the thing: If I don’t know my own data, I can’t answer those questions. AI is only as good as what I bring to the conversation. Without years of embedded contextual knowledge, it is just guessing.

Early in my career, when I told my colleague how lost I felt and overwhelmed I was, she gave it to me straight: I had been thrown into the deep ocean and had to sink or swim. Initially I thought, how can someone be so straight forward? Later I realized that most data environments are exactly like that. Nobody hands you a life jacket. The individuals who survive are those who master the waters and figure out how to swim — and then build the life jacket so the next person doesn’t have to.

Through discussion with colleagues and friends who are interested in data analytics and data engineering, I have observed that some people are reluctant to enter into the domain thinking AI might limit the opportunities.

My advice is to target overlooked areas. AI can definitely handle tasks, but you need to train it with the right knowledge first. That knowledge and those insights need to come from someone who is actively engaged in the domain, has hand-on experience with the day-to-day work and understands the why behind it. Be that practitioner.

About the author

Vinit Rajguru

Vinit Rajguru is a Senior Solution Consultant specializing in marketing data infrastructure and audience strategy at a global technology firm. He helps organizations build data pipelines, implement customer data platforms, and use artificial intelligence driven targeting to reach the right customers. He writes about the intersection of AI, data engineering, and modern marketing technology.

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

Interview with Udaya Bhaskar Vemuri, Senior Application Security Analyst

Interview with Udaya Bhaskar Vemuri, Senior Application Security Analyst

(Featured) - Vemuri discusses approved AI models, evidence-based findings, architecture context and collaboration with application teams.

Edited by Haley Spracale, Editor at Featured News · Nov 3, 2026

As a Senior Application Security Analyst, how would you describe your work in application security and the perspective you bring to secure design reviews?

As an application security engineer/architect, my goal is always to build secure application designs and work toward a shift-left design model. Secure design reviews (SDR) help in designing secure architectures and identifying flaws early in the software development life cycle (SDLC) process. Designs should also be scalable to support future-oriented AI designs and other capabilities.

What path led you to become a Senior Application Security Analyst, and how did secure design reviews become an important part of your work?

I started my career in security, and I came to love the work I did. Secure design reviews became especially interesting to me because they are the foundation of any application design. If an application's architecture or design is secure, the application tends to withstand attacks better than it would by relying only on front-end protections such as network firewalls and web application firewalls.

When you first began using an LLM-based assistant in design-review preparation, what practical problem were you trying to solve?

It’s been more than a year now. I was trying to solve the problem of keeping application security in step with the speed at which applications need to grow and scale their features to meet customer needs, so that security would never become a bottleneck for development teams. This is where AI-based reviews with human intervention help speed up reviews, prevent security from becoming a bottleneck, and ultimately deliver a secure application.

How do you decide which application materials and review tasks are appropriate to share with an AI assistant, particularly when handling sensitive technical information?

The AI model should have gone through its due diligence with the technology risk assessment teams and been approved by the compliance and security teams before you start sharing details with it. Nowadays, many major vendors offer on-premises options on an isolated network for your company, where they don't use your data to train the AI model. Once you have an approved AI model, you can share architecture diagrams and other details to conduct a secure design review.

What structured context do you provide an AI assistant to get useful early insights into an application’s architecture, data flows, and likely threat areas?

So, once the application teams share the architecture diagrams, data flow diagrams, and C1, C2, and C3 diagrams, we can run them through the AI and ask it to provide evidence-based results and explain, for each vulnerability, why it considers the application vulnerable, what part of the design triggered the vulnerability, and why it assigned that severity. This way, you will get an evidence-based result from the AI, and then you can manually question each finding.

Can you describe how you validate AI-generated review questions or observations before they influence a security finding or risk decision?

The configuration I set, or the prompt I give the AI, is to do SDR reviews using industry standards for findings and risk determination. Then, I send a list of questions to my internal app team to find out what kind of data the app handles and whether it is internally or externally facing. These are some generic questions that help the AI determine the risk. At the end of this process, there will be human validation.

Where have you found AI assistance most valuable in helping uncover gaps around authentication, authorization, integrations, or data handling during a design review?

I have found AI most valuable when reviewing complex designs and comparing them with previous design releases, as it can relate the overall architecture, data flow, and API or other integrations. It helps uncover issues related to authorization, authentication, integrations, and data handling if you provide the right prompt, ask the right questions, and give the AI the exact details it needs to evaluate the design.

How do you keep AI-assisted reviews collaborative with engineering teams rather than allowing the tool’s output to become a substitute for technical discussion and evidence?

I treat AI as a supporting tool for speeding up reviews rather than as a final decision-maker. A human always makes the final decisions. We go back and forth with questions to application teams to address assumptions AI makes when highlighting a finding. In this way, neither AI nor I make assumptions; instead, we deliver findings based on evidence. This also helps us understand the actual risk.

For application security teams starting with AI-assisted secure design reviews, what is the first human-led process or guardrail you would put in place, and why?

As I’ve said throughout., evidence-based output and human validation are the first and last guardrails I would put in place. AI might not understand the complete architecture. For example, it might flag a GDPR issue, but the compliance team may have already addressed it. Rather than sending the finding, first check with the app teams to see whether they have that data or those rules in place. This helps ensure a better secure design review using AI.

Thanks for sharing your knowledge and expertise. Is there anything else you'd like to add?

Yes, AI is developing at a fast pace, and application development is too. We can integrate with TFS or Git, read the full code, and ask the AI itself to give you the C1, C2, and C3 diagrams. Then you can send the diagrams to the app team to validate. In this way, the app team's burden is reduced, and they will be happy to collaborate. Happy exploring AI.

About the expert

Udaya Bhaskar Vemuri

Udaya Bhaskar VemuriSenior Application Security Analyst

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

American AI Models Must Become the Global Default

(NewsUSA) - Leadership in artificial intelligence may come down to adoption: technological leadership matters only if American AI becomes the default choice for governments, companies, and developers, according to a new memo from the Special Competitive Studies Project (SCSP), a nonprofit and nonpartisan initiative with a goal of making recommendations to strengthen America’s long-term competitiveness in artificial intelligence.

In the memo, “The Open Frontier: How America Wins the AI Diffusion Race,” SCSP staff explained that open models will help determine which technology ecosystem becomes the global default. Although the U.S. led the world in wireless research, Huawei won the diffusion race and connected much of the globe by out-competing on cost, financing, and speed of deployment, and China is implementing a similar strategy with AI. Its capable, low-cost, downloadable models are drawing developers: the memo notes that developer adoption has shifted measurably toward Chinese open models. The advantage, the memo says, comes not from openness itself but from the adoption it enables.

The United States needs a strategy that builds on its distinctive strengths. While there are trust and security concerns regarding Chinese open models, the American response should be to strengthen its own open model ecosystem, according to the memo. Currently, leading U.S. frontier laboratories monetize access through subscriptions, enterprise products, and managed platforms. But a strong American strategy should also support open model developers and the researchers, startups, and businesses that build on their work.

The memo outlines three lines of effort:

● Build the AI Ecosystem America Can Win. Expanding access to compute, capital, and shared infrastructure will support the development of a thriving open AI ecosystem. Researchers, startups, and governments can then inspect, adapt, and trust American models.

● Turn Leadership into Adoption. Fund tools that show a model works for its purpose, aggregate and share working deployments, and measure cost, time to complete, and mission outcomes to accelerate adoption of American AI across society.

● Govern American AI Without Making It Inaccessible. Govern risk based on what models can do, how they are used, and their impacts and outcomes, not simply whether their weights are public.

Visit scsp.ai to learn more and to read the full report.

Your Business Has a Reputation Beyond Its Website. What Does It Say?

(NewsUSA) - A business owner may know exactly what appears on the company’s homepage. The broader online picture can be harder to track.

An older interview, a news feature or a description on another website may tell part of the company’s story. Taken together, those materials form a public record that extends beyond the messages a business publishes itself.

As consumers use artificial intelligence to research companies and compare options, that wider record deserves attention.

The question is no longer simply whether information about a business exists online. It is whether that information accurately explains what the business does and the expertise it offers.

Look at Your Business From the Outside

A useful starting point is to consider what a prospective customer would want to know.

What services does the company provide? Who does it serve? What experience do its professionals bring? Is there useful information explaining how they approach common customer problems?

A polished website can answer some of those questions. Articles, interviews and other publicly available materials can add context.

Business owners can review those sources for outdated details, unclear descriptions and missing information. They can also examine whether the topics associated with their company reflect the work they do today.

Local Stories Can Show Practical Expertise

Local and regional news outlets offer a setting for information that connects business knowledge with everyday concerns.

A seasonal home-maintenance article can explain problems residents may encounter. A technology feature can help small-business owners understand a changing industry. An educational story can introduce readers to professionals whose experience is relevant to their needs.

The strongest contribution is specific and useful. Rather than relying on broad claims about being a leader, a company can demonstrate its knowledge by explaining a topic well.

NewsUSA has worked with newspaper and digital news partners since 1987 to distribute consumer-oriented feature stories. Its services give organizations a way to share educational content beyond their own websites.

Check the Picture AI Presents

An AI response offers another view of how a company is represented online.

Does the response describe the business accurately? Which competitors appear? What sources, if any, does the platform cite?

NewsUSA’s AI Authority Audit examines brand descriptions across ChatGPT, Claude, Gemini, Perplexity and Grok, with citation evidence and competitor comparisons. Businesses can learn more or request an audit at NewsUSA.ai.

The findings should be treated as a snapshot. AI responses can vary, and an article’s publication does not ensure that a platform will reference it or recommend the company.

For businesses, the lasting priority is an accurate, useful public presence. That means keeping company information current and contributing explanations that help people understand the problems the business solves.

A reputation develops wherever people encounter a company’s name. Giving them clear information helps make those encounters more meaningful.

When Customers Ask AI for Advice, Will They Find Your Business?

(NewsUSA) - Before contacting a company, a potential customer may have a question: What should I look for in a contractor? How do I compare service providers? Which businesses can help solve my problem?

Artificial intelligence gives consumers another way to explore those questions. Instead of reviewing individual search results, they can ask an AI assistant to explain their options and suggest what to consider.

For businesses, that creates a reason to look beyond whether their website appears in a search. They also need to consider whether useful information about their expertise is available when someone begins researching a decision.

Start With the Questions Customers Already Ask

Businesses often have valuable educational material hiding in everyday conversations.

A home-services company may regularly explain how to recognize maintenance problems. A technology provider may help customers understand which features they need. A financial professional may answer questions about preparing for retirement.

Those conversations can become the foundation for informative articles that help people understand a subject before choosing a provider.

The starting point is simple: Identify a common customer question and answer it clearly. Explain unfamiliar terms, offer practical examples and support factual claims with reliable sources.

An article that helps readers make sense of a problem gives them a concrete reason to recognize a company’s expertise.

Make Expertise Available Beyond Your Website

A company website remains an important source of information about its services and people. Publishing useful material elsewhere can extend that information to audiences who have never visited the site.

“Companies have traditionally concentrated on what Google sees when someone searches for them,” said Rick Smith, founder of NewsUSA. “Now they also have to think about what AI systems find when someone asks about their company, their competitors or their entire industry.”

Founded in 1987, NewsUSA distributes educational feature stories through newspaper and digital news partners, helping businesses communicate their knowledge to broader audiences.

For readers, the value comes from the information itself: Does the story answer the question? Is the explanation understandable? Does it help them decide what to do next?

Find Out How AI Describes Your Company

Businesses can also examine how their existing online presence appears in AI responses.

NewsUSA’s AI Authority Audit evaluates how ChatGPT, Claude, Gemini, Perplexity and Grok describe a brand, examining cited sources and gaps compared with competitors.

That review can provide a starting point for understanding the information people may encounter while researching a company or its market.

Publishing an article does not guarantee an AI citation or recommendation. Responses can change, and visibility depends on multiple factors.

Still, businesses can take a practical step today: Make their knowledge easier to find and understand.

The questions customers ask are already there. Clear, useful answers give a business something meaningful to contribute.

Learn more at NewsUSA.ai.

Battle for Biotech Leadership: U.S. vs. China

(NewsUSA) - The battle for global leadership in biotechnology is not won or lost in a single field, but is spread across areas including supply chains, manufacturing capacity, data holdings, and regulatory speed. The United States still holds the lead over China, but it is narrowing, according to the latest Biotech Scorecard from the Special Competitive Studies Project (SCSP), a nonprofit and nonpartisan initiative with a goal of making recommendations to strengthen America's long-term competitiveness in artificial intelligence.

The SCSP’s Tech Scorecard methodology involves a five-point analysis of elements including Innovation Leadership, Market Ecosystem, Talent Pipeline, Industrial Capacity, and National Leverage.

Although the United States has the lead in Innovation Leadership, Market Ecosystem, and Talent Pipeline, China appears ahead in terms of Industrial Capacity and National Leverage, according to the report. 

China has the potential to overtake the U.S. in biotechnology by 2030, strengthened by two decades of deliberate national strategy that is now producing results. By contrast, the American position is “a return on research investments made decades ago, sustained by a capital market that rewards its strongest performers,” according to SCSP’s analysts. 

The report focuses on the biopharmaceuticals sector of biotechnology as examples of China’s acceleration in National Leverage and Industrial capacity. Most government funding for biotechnology in the United States goes to basic research. 

Unfortunately, a lack of urgency persists in expanding government support to commercialization of drug products, for example. “Approval timelines for drugs entering clinical trials and going to domestic markets are driven by government policy, and can help accelerate, or slow down, the pipeline of innovation,” the SCSP authors emphasize.

Although the United States and China both invest in basic research, China is more active in supporting biotech startups through the process of acquiring capital to build pilot capacity, scale up production, and reach markets, without waiting for a definitive return on these expanded investments. This strategy includes preferential taxation, below-market lending, and direct subsidies. The U.S. tends to leave this aspect of biotechnology development to the private sector.

Looking ahead, as artificial intelligence allows scientists to predict molecular activity, the expensive early stages of drug discovery will likely decrease, and the competitive advantage will shift to testing, manufacturing, and commercializing a promising drug candidate.

“Whether the United States retains its edge depends both on model quality and how quickly it can move a computationally generated candidate through trials, approval, and manufacture before a competitor improves on it,” according to the report.

To read the full report and learn more, visit scsp.ai.

Subscribe to Technology